public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Peter Osterlund <petero2@telia.com>
Cc: Akinobu Mita <akinobu.mita@gmail.com>,
	linux-kernel@vger.kernel.org,
	Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH] blk-core: use BIO list management functions
Date: Tue, 23 Feb 2010 23:23:00 +0100	[thread overview]
Message-ID: <20100223222300.GR1025@kernel.dk> (raw)
In-Reply-To: <alpine.LFD.2.00.1002231937330.12278@localhost>

On Tue, Feb 23 2010, Peter Osterlund wrote:
> On Tue, 23 Feb 2010, Jens Axboe wrote:
>
>> On Tue, Feb 23 2010, Akinobu Mita wrote:
>>> 2010/2/23 Jens Axboe <jens.axboe@oracle.com>:
>>>> On Mon, Feb 22 2010, Akinobu Mita wrote:
>>>>> Now that the bio list management stuff is generic, convert
>>>>> generic_make_request to use bio lists instead of its own private bio
>>>>> list implementation.
>>>>
>>>> Looks good, applied. Also saves 4 bytes in task_struct, not a bad thing
>>>> :-)
>>>
>>> Thanks.
>>>
>>> How about another cleanup patch for pktcdvd?
>>> http://lkml.org/lkml/2010/2/22/93
>>
>> Looks fine to me, I can pick it up if need be. Peter?
>
> It looks fine to me too. Please pick it up, Jens.

Certainly, I'll queue it up for 2.6.34. I'm assuming I can add your
acked-by?

-- 
Jens Axboe


  reply	other threads:[~2010-02-23 22:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-22 13:29 [PATCH] pktcdvd: use BIO list management functions Akinobu Mita
2010-02-22 13:29 ` [PATCH] blk-core: " Akinobu Mita
2010-02-23  7:55   ` Jens Axboe
2010-02-23 14:26     ` Akinobu Mita
2010-02-23 14:53       ` Jens Axboe
2010-02-23 18:38         ` Peter Osterlund
2010-02-23 22:23           ` Jens Axboe [this message]
2010-02-23 22:26             ` Peter Osterlund

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=20100223222300.GR1025@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=akinobu.mita@gmail.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=petero2@telia.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