From: Bob Liu <lliubbo@gmail.com>
To: David Rientjes <rientjes@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, Andi Kleen <andi@firstfloor.org>
Subject: Re: [Patch] mempolicy: remove redundant code
Date: Sat, 13 Mar 2010 13:03:48 +0800 [thread overview]
Message-ID: <cf18f8341003122103i3164a28h4aea908507a6e12e@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1003121236060.13400@chino.kir.corp.google.com>
On Sat, Mar 13, 2010 at 4:37 AM, David Rientjes <rientjes@google.com> wrote:
> On Fri, 12 Mar 2010, Bob Liu wrote:
>
>> 1. In funtion is_valid_nodemask(), varibable k will be inited to 0 in
>> the following loop, needn't init to policy_zone anymore.
>>
>> 2. (MPOL_F_STATIC_NODES | MPOL_F_RELATIVE_NODES) has already defined
>> to MPOL_MODE_FLAGS in mempolicy.h.
>>
>> Signed-off-by: Bob Liu <lliubbo@gmail.com>
>
> I like your patch, but it has whitespace damage. Would it be possible to
> read the gmail section of Documentation/email-clients.txt and try to
> repropose it? Thanks.
>
I am sorry for that, I have resend that patch. Thanks a lot for your reply.
--
Regards,
-Bob Liu
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-03-13 5:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-12 10:24 [Patch] mempolicy: remove redundant code Bob Liu
2010-03-12 20:37 ` David Rientjes
2010-03-13 5:03 ` Bob Liu [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-03-13 5:01 [PATCH] " Bob Liu
2010-03-13 9:52 ` David Rientjes
2010-03-13 12:33 ` Bob Liu
2010-03-14 11:50 Bob Liu
2010-03-14 23:18 ` David Rientjes
2010-03-15 1:11 ` Bob Liu
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=cf18f8341003122103i3164a28h4aea908507a6e12e@mail.gmail.com \
--to=lliubbo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).