From: Jens Axboe <axboe@suse.de>
To: Tejun Heo <htejun@gmail.com>
Cc: James.Bottomley@steeleye.com, bzolnier@gmail.com,
jgarzik@pobox.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH Linux 2.6.12-rc5-mm1 00/06] blk: barrier flushing reimplementation
Date: Sun, 29 May 2005 21:14:37 +0200 [thread overview]
Message-ID: <20050529191437.GA30586@suse.de> (raw)
In-Reply-To: <20050529042034.5FF4CF1C@htj.dyndns.org>
On Sun, May 29 2005, Tejun Heo wrote:
> Hello, guys.
>
> This patchset is reimplementation of QUEUE_ORDERED_FLUSH feature. It
> doens't update API docs yet. If it's determined that this patchset
> can go in, I'll regenerate this patchset with doc updates (sans the
> last debug message patch of course).
Awesome work, that's really the last step in getting the barrier code
fully unified and working with tags. I'll review your patchset tomorrow.
--
Jens Axboe
next prev parent reply other threads:[~2005-05-29 19:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-29 4:23 [PATCH Linux 2.6.12-rc5-mm1 00/06] blk: barrier flushing reimplementation Tejun Heo
2005-05-29 4:23 ` [PATCH Linux 2.6.12-rc5-mm1 01/06] blk: add @uptodate to end_that_request_last() and @error to rq_end_io_fn() Tejun Heo
2005-05-29 4:23 ` [PATCH Linux 2.6.12-rc5-mm1 02/06] blk: make scsi use -EOPNOTSUPP instead of -EIO on ILLEGAL_REQUEST Tejun Heo
2005-05-29 4:23 ` [PATCH Linux 2.6.12-rc5-mm1 03/06] blk: make ide use -EOPNOTSUPP instead of -EIO on ABRT_ERR Tejun Heo
2005-05-29 4:23 ` [PATCH Linux 2.6.12-rc5-mm1 04/06] blk: reimplement QUEUE_OREDERED_FLUSH Tejun Heo
2005-05-29 9:54 ` Tejun Heo
2005-05-29 4:23 ` [PATCH Linux 2.6.12-rc5-mm1 05/06] blk: turn on QUEUE_ORDERED_FLUSH by default if ordered tag isn't supported Tejun Heo
2005-05-29 4:23 ` [PATCH Linux 2.6.12-rc5-mm1 06/06] blk: debug messages Tejun Heo
2005-05-29 17:37 ` [PATCH Linux 2.6.12-rc5-mm1 00/06] blk: barrier flushing reimplementation Jeff Garzik
2005-05-29 19:14 ` Jens Axboe [this message]
2005-05-30 11:31 ` Jens Axboe
2005-05-30 19:38 ` Tejun Heo
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=20050529191437.GA30586@suse.de \
--to=axboe@suse.de \
--cc=James.Bottomley@steeleye.com \
--cc=bzolnier@gmail.com \
--cc=htejun@gmail.com \
--cc=jgarzik@pobox.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 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.