From: Andrew Morton <akpm@linux-foundation.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Hugh Dickins <hughd@google.com>, Mel Gorman <mel@csn.ul.ie>
Subject: Re: [PATCH] mm: Fix wrong kunmap_atomic() pointer
Date: Fri, 3 Jun 2011 21:14:22 -0700 [thread overview]
Message-ID: <20110603211422.3db036df.akpm@linux-foundation.org> (raw)
In-Reply-To: <1307158665.3667.86.camel@gandalf.stny.rr.com>
On Fri, 03 Jun 2011 23:37:45 -0400 Steven Rostedt <rostedt@goodmis.org> wrote:
> Running a ktest.pl test, I hit the following bug on x86_32:
Damn, that sounds like a useful tool. You should tell people about it!
next prev parent reply other threads:[~2011-06-04 4:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-04 3:37 [PATCH] mm: Fix wrong kunmap_atomic() pointer Steven Rostedt
2011-06-04 3:54 ` Steven Rostedt
2011-06-04 4:14 ` Andrew Morton [this message]
2011-06-05 19:20 ` Hugh Dickins
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=20110603211422.3db036df.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=a.p.zijlstra@chello.nl \
--cc=hughd@google.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mel@csn.ul.ie \
--cc=rostedt@goodmis.org \
/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