From: Christoph Hellwig <hch@infradead.org>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Harvey Harrison <harvey.harrison@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] block: kmalloc args reversed, small function definition fixes
Date: Thu, 28 Aug 2008 10:30:55 -0400 [thread overview]
Message-ID: <20080828143055.GA10469@infradead.org> (raw)
In-Reply-To: <20080828142800.GG20055@kernel.dk>
On Thu, Aug 28, 2008 at 04:28:00PM +0200, Jens Axboe wrote:
> > > Woops, that kmalloc() is nasty. Thanks a lot, applied to for-2.6.28.
> >
> > Umm, the gfp bit sounds like a clear 2.6.27 candidate.
>
> I would agree, except the bug is introduced by a patch in the 2.6.28
> series :-)
Ah, okay. Makes sense then.
prev parent reply other threads:[~2008-08-28 14:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-27 20:24 [PATCH] block: kmalloc args reversed, small function definition fixes Harvey Harrison
2008-08-28 7:26 ` Jens Axboe
2008-08-28 14:19 ` Christoph Hellwig
2008-08-28 14:28 ` Jens Axboe
2008-08-28 14:30 ` Christoph Hellwig [this message]
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=20080828143055.GA10469@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=harvey.harrison@gmail.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.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