From: Tejun Heo <htejun@gmail.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Jens Axboe <jens.axboe@oracle.com>,
linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org,
fujita.tomonori@lab.ntt.co.jp,
James.Bottomley@HansenPartnership.com,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCHSET #upstream] block/libata: update and use block layer padding and draining
Date: Sat, 09 Feb 2008 09:22:16 +0900 [thread overview]
Message-ID: <47ACF238.3030605@gmail.com> (raw)
In-Reply-To: <47ACCE33.9090809@garzik.org>
Jeff Garzik wrote:
> Jens Axboe wrote:
>> On Fri, Feb 08 2008, Jeff Garzik wrote:
>>> Jeff Garzik wrote:
>>>> Tejun Heo wrote:
>>>>> This patchset updates block layer padding and draining support and
>>>>> make libata use it. It's based on James Bottomley's initial work and,
>>>>> of the five, the last two patches are from James with some
>>>>> modifications.
>>>>>
>>>>> Please read the following thread for more info.
>>>>>
>>>>> http://thread.gmane.org/gmane.linux.scsi/37185
>>>>>
>>>>> This patchset is on top of
>>>>>
>>>>> upstream (a6af42fc9a12165136d82206ad52f18c5955ce87)
>>>>> + kill-n_iter-and-fix-fsl patch [1]
>>>> ACK patchset... lets definitely get these fixes upstream.
>>>>
>>>> Once Jens is happy, I would prefer the merge the lot upstream, if
>>>> that is OK with everyone involved?
>>> Jens, ping?
>>>
>>> It's a bug fix, so it would be nice to get this in soonish. As
>>> noted, if all looks good, I would prefer to merge via libata-dev...
>>
>> I'm ok with it, but lets please merge the block bits through the block
>> repo, since they are not trivial. Wont be until the week after next,
>> though.
>
> hmmm, rather than delaying the bug fixes for two weeks, since you're OK
> with it we can push upstream now, and apply further fixes if problems
> arise during testing?
>
> I would rather get these fixes out into wide testing sooner rather than
> later.
I have an updated version. Please standby a bit.
Thanks.
--
tejun
prev parent reply other threads:[~2008-02-09 0:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-05 7:53 [PATCHSET #upstream] block/libata: update and use block layer padding and draining Tejun Heo
2008-02-05 7:53 ` [PATCH 1/5] block: update bio according to DMA alignment padding Tejun Heo
2008-02-05 7:53 ` [PATCH 2/5] block: add request->raw_data_len Tejun Heo
2008-02-05 7:53 ` [PATCH 3/5] block: implement request_queue->dma_drain_needed Tejun Heo
2008-02-05 7:53 ` [PATCH 4/5] libata: eliminate the home grown dma padding in favour of that provided by the block layer Tejun Heo
2008-02-05 7:53 ` [PATCH 5/5] libata: implement drain buffers Tejun Heo
2008-02-06 23:31 ` [PATCHSET #upstream] block/libata: update and use block layer padding and draining James Bottomley
2008-02-07 0:09 ` Jeff Garzik
2008-02-08 20:56 ` Jeff Garzik
2008-02-08 21:04 ` Jens Axboe
2008-02-08 21:48 ` Jeff Garzik
2008-02-09 0:22 ` Tejun Heo [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=47ACF238.3030605@gmail.com \
--to=htejun@gmail.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=jeff@garzik.org \
--cc=jens.axboe@oracle.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.