All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wang Sheng-Hui <shhuiw@gmail.com>
To: David Rientjes <rientjes@google.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/mempolicy.c: use enum value MPOL_REBIND_ONCE instead of 0 in mpol_rebind_policy
Date: Mon, 19 Dec 2011 13:20:08 +0800	[thread overview]
Message-ID: <4EEEC988.2060309@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1112181444530.1364@chino.kir.corp.google.com>

On 2011a1'12ae??19ae?JPY 06:45, David Rientjes wrote:
> 
> On Sat, 17 Dec 2011, Wang Sheng-Hui wrote:
> 
>>> Tip: when proposing patches, it's helpful to run scripts/get_maintainer.pl 
>>> on your patch file from git to determine who should be cc'd on the email.
>>
>> Thanks for your tip.
>> I have tried the script with option -f, and only get the mm, kernel mailing
>> lists, no specific maintainer provided. So here I just posted the patch to 
>> these 2 lists.
>>
> 
> $ ./scripts/get_maintainer.pl -f mm/mempolicy.c
> Andrew Morton <akpm@linux-foundation.org> (commit_signer:19/23=83%)
> KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> (commit_signer:8/23=35%)
> Stephen Wilson <wilsons@start.ca> (commit_signer:6/23=26%)
> Andrea Arcangeli <aarcange@redhat.com> (commit_signer:5/23=22%)
> Johannes Weiner <hannes@cmpxchg.org> (commit_signer:3/23=13%)
> linux-mm@kvack.org (open list:MEMORY MANAGEMENT)
> linux-kernel@vger.kernel.org (open list)
> 
> All of those people should be cc'd on patches touching mm/mempolicy.c.
Got it. Thanks,

--
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>

WARNING: multiple messages have this Message-ID (diff)
From: Wang Sheng-Hui <shhuiw@gmail.com>
To: David Rientjes <rientjes@google.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/mempolicy.c: use enum value MPOL_REBIND_ONCE instead of 0 in mpol_rebind_policy
Date: Mon, 19 Dec 2011 13:20:08 +0800	[thread overview]
Message-ID: <4EEEC988.2060309@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1112181444530.1364@chino.kir.corp.google.com>

On 2011年12月19日 06:45, David Rientjes wrote:
> 
> On Sat, 17 Dec 2011, Wang Sheng-Hui wrote:
> 
>>> Tip: when proposing patches, it's helpful to run scripts/get_maintainer.pl 
>>> on your patch file from git to determine who should be cc'd on the email.
>>
>> Thanks for your tip.
>> I have tried the script with option -f, and only get the mm, kernel mailing
>> lists, no specific maintainer provided. So here I just posted the patch to 
>> these 2 lists.
>>
> 
> $ ./scripts/get_maintainer.pl -f mm/mempolicy.c
> Andrew Morton <akpm@linux-foundation.org> (commit_signer:19/23=83%)
> KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> (commit_signer:8/23=35%)
> Stephen Wilson <wilsons@start.ca> (commit_signer:6/23=26%)
> Andrea Arcangeli <aarcange@redhat.com> (commit_signer:5/23=22%)
> Johannes Weiner <hannes@cmpxchg.org> (commit_signer:3/23=13%)
> linux-mm@kvack.org (open list:MEMORY MANAGEMENT)
> linux-kernel@vger.kernel.org (open list)
> 
> All of those people should be cc'd on patches touching mm/mempolicy.c.
Got it. Thanks,

  reply	other threads:[~2011-12-19  5:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-14 13:28 [PATCH] mm/mempolicy.c: use enum value MPOL_REBIND_ONCE instead of 0 in mpol_rebind_policy Wang Sheng-Hui
2011-12-14 13:28 ` Wang Sheng-Hui
2011-12-15  2:42 ` David Rientjes
2011-12-15  2:42   ` David Rientjes
2011-12-17 13:47   ` Wang Sheng-Hui
2011-12-17 13:47     ` Wang Sheng-Hui
2011-12-18 22:45     ` David Rientjes
2011-12-18 22:45       ` David Rientjes
2011-12-19  5:20       ` Wang Sheng-Hui [this message]
2011-12-19  5:20         ` Wang Sheng-Hui

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=4EEEC988.2060309@gmail.com \
    --to=shhuiw@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=rientjes@google.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.