From: Steven Rostedt <rostedt@goodmis.org>
To: Michal Hocko <mhocko@suse.cz>
Cc: LKML <linux-kernel@vger.kernel.org>,
Johannes Weiner <hannes@cmpxchg.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>,
Balbir Singh <balbir@linux.vnet.ibm.com>,
Minchan Kim <minchan.kim@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Dave Hansen <dave@linux.vnet.ibm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Randy Dunlap <rdunlap@xenotime.net>
Subject: Re: [PATCH v2] cgroup/kmemcheck: Annotate alloc_page() for cgroup allocations
Date: Tue, 26 Jul 2011 15:04:48 -0400 [thread overview]
Message-ID: <1311707088.21143.0.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <20110726184342.GB26597@tiehlicka.suse.cz>
On Tue, 2011-07-26 at 20:43 +0200, Michal Hocko wrote:
> Maybe just a nit. What about making
> gfp_t flags = GFP_KERNEL | __GFP_NOWARN;
> and use it at both places?
I actually thought about that, but was too lazy to do it ;)
>
> Anyway feel free to add my:
> Reviewed-by: Michal Hocko <mhocko@suse.cz>
>
Thanks, I'll send out a v3 with the updates.
-- Steve
next prev parent reply other threads:[~2011-07-26 19:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-26 17:05 [PATCH] cgroup/kmemcheck: No need to annotate base anymore Steven Rostedt
2011-07-26 17:38 ` Michal Hocko
2011-07-26 17:41 ` Steven Rostedt
2011-07-26 17:44 ` Steven Rostedt
2011-07-26 18:17 ` [PATCH v2] cgroup/kmemcheck: Annotate alloc_page() for cgroup allocations Steven Rostedt
2011-07-26 18:43 ` Michal Hocko
2011-07-26 19:04 ` Steven Rostedt [this message]
2011-07-26 19:19 ` [PATCH v3] " Steven Rostedt
2011-07-26 22:13 ` Johannes Weiner
2011-07-26 23:03 ` Minchan Kim
2011-07-27 0:55 ` KAMEZAWA Hiroyuki
2011-08-12 9:58 ` Catalin Marinas
2011-07-27 2:10 ` [PATCH v3 RESEND] " Steven Rostedt
2011-07-29 13:31 ` Steven Rostedt
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=1311707088.21143.0.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=catalin.marinas@arm.com \
--cc=dave@linux.vnet.ibm.com \
--cc=hannes@cmpxchg.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=minchan.kim@gmail.com \
--cc=nishimura@mxp.nes.nec.co.jp \
--cc=rdunlap@xenotime.net \
/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
all inboxes | Powered by JetHome®