From: Jens Axboe <jens.axboe@oracle.com>
To: Kiyoshi Ueda <k-ueda@ct.jp.nec.com>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
dm-devel@redhat.com, j-nomura@ce.jp.nec.com
Subject: Re: [PATCH 0/3] block changes for request-based dm-multipath
Date: Thu, 18 Sep 2008 18:25:06 +0200 [thread overview]
Message-ID: <20080918162505.GL20055@kernel.dk> (raw)
In-Reply-To: <20080918.104356.74754407.k-ueda@ct.jp.nec.com>
On Thu, Sep 18 2008, Kiyoshi Ueda wrote:
> Hi Jens,
>
> The following patches are changes of the block layer for
> request-based dm-multipath.
> The patches are created on the following commit of for-2.6.28
> in linux-2.6-block.
Thank you, I've merged these three patches.
--
Jens Axboe
prev parent reply other threads:[~2008-09-18 16:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-18 14:43 [PATCH 0/3] block changes for request-based dm-multipath Kiyoshi Ueda
2008-09-18 14:45 ` [PATCH 1/3] block: add request update interface Kiyoshi Ueda
2008-09-18 14:45 ` [PATCH 2/3] block: add request submission interface Kiyoshi Ueda
2008-09-18 14:46 ` [PATCH 3/3] block: add a queue flag for request stacking support Kiyoshi Ueda
2008-09-18 16:25 ` Jens Axboe [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=20080918162505.GL20055@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=dm-devel@redhat.com \
--cc=j-nomura@ce.jp.nec.com \
--cc=k-ueda@ct.jp.nec.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox