From: David Rientjes <rientjes@google.com>
To: Prasad Joshi <prasadjoshi124@gmail.com>
Cc: linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
Anand Mitra <mitra@kqinfotech.com>
Subject: Re: [RFC][PATCH 00/25]: Propagating GFP_NOFS inside __vmalloc()
Date: Fri, 11 Mar 2011 15:08:32 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.00.1103111505450.4900@chino.kir.corp.google.com> (raw)
In-Reply-To: <AANLkTimu-42CC3pv57njj6-UqwDO3iNLtiem9=y9ggng@mail.gmail.com>
On Fri, 11 Mar 2011, Prasad Joshi wrote:
> Thanks a lot for your reply. I should have seen your mail before
> sending 23 mails :(
> I will make the changes suggested by you and will resend all of the
> patches again.
>
Thanks for taking this effort on. A couple other points:
- each patch should have a different subject prefixed with the subsystem
that it touches (for example: "x86: add gfp flags variant of
pte_alloc_one") and the maintainers should be cc'd. Check
scripts/get_maintainer.pl or the MAINTAINERS file. Also, for changes
that touch all arch code you'll want to cc linux-arch@vger.kernel.org
as well.
- each change needs to have a proper changelog prior to your
signed-off-by line to explain why the change is being done and in
preparation for supporting non-GFP_KERNEL allocations from __vmalloc().
--
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-11 23:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-11 20:35 Prasad Joshi
2011-03-11 21:01 ` David Rientjes
2011-03-11 21:13 ` Prasad Joshi
2011-03-11 23:08 ` David Rientjes [this message]
2011-03-12 2:05 ` Anand Mitra
2011-03-13 1:22 ` David Rientjes
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.DEB.2.00.1103111505450.4900@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=mitra@kqinfotech.com \
--cc=prasadjoshi124@gmail.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