From: Jiri Kosina <jkosina@suse.cz>
To: "Justin P. Mattock" <justinmattock@gmail.com>
Cc: linux-kernel@vger.kernel.org, Vinod Koul <vinod.koul@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
Wim Van Sebroeck <wim@iguana.be>,
linux-watchdog@vger.kernel.org,
Greg Kroah-Hartman <gregkh@suse.de>,
Alan Stern <stern@rowland.harvard.edu>,
linux-usb@vger.kernel.org, Chris Mason <chris.mason@oracle.com>,
Eric Paris <eparis@redhat.com>,
John McCutchan <john@johnmccutchan.com>,
Robert Love <rlove@rlove.org>,
Andrew Morton <akpm@linux-foundation.org>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
linux-mm@kvack.org, Hugh Dickins <hughd@google.com>
Subject: Re: [PATCH 00/00]Remove one to many n's in a word.
Date: Tue, 1 Mar 2011 15:12:30 +0100 (CET) [thread overview]
Message-ID: <alpine.LNX.2.00.1103011507120.32580@pobox.suse.cz> (raw)
In-Reply-To: <1298781250-2718-17-git-send-email-justinmattock@gmail.com>
On Sat, 26 Feb 2011, Justin P. Mattock wrote:
> The Patch below removes one to many "n's" in a word..
Hi Justin,
I have applied all the patches from the series which were not present in
linux-next as of today (in a squashed-together form, no need to have
separated commits for such cosmetic changes).
I'd suggest that, unless any subsystem maintainer explicitly states
otherwise, you submit all such similar changes justo to trivial@kernel.org
(and perhaps CC LKML). I propose this because:
- I believe most maintainers don't care about these changes and don't need
to be bothered
- it reduces annoying mail traffic (tens of mails because such
nano-change)
- it reduces the trivial tree maintainership load, as I don't have to wait
and cross-check which maintainer has applied which bits and which ones
were not picked up
--
Jiri Kosina
SUSE Labs, Novell Inc.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-03-01 14:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1298781250-2718-1-git-send-email-justinmattock@gmail.com>
2011-02-27 4:34 ` [PATCH 15/17]mm:mempolicy.c Remove " Justin P. Mattock
2011-02-27 4:34 ` [PATCH 16/17]mm:shmem.c " Justin P. Mattock
2011-03-01 14:12 ` Jiri Kosina [this message]
2011-03-01 15:30 ` [PATCH 00/00]Remove " Justin Mattock
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LNX.2.00.1103011507120.32580@pobox.suse.cz \
--to=jkosina@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=chris.mason@oracle.com \
--cc=dan.j.williams@intel.com \
--cc=eparis@redhat.com \
--cc=gregkh@suse.de \
--cc=hughd@google.com \
--cc=john@johnmccutchan.com \
--cc=justinmattock@gmail.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=rlove@rlove.org \
--cc=stern@rowland.harvard.edu \
--cc=vinod.koul@intel.com \
--cc=wim@iguana.be \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox