From: Ming Lei <ming.lei@redhat.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
ZiyangZhang <ZiyangZhang@linux.alibaba.com>
Subject: Re: [PATCH V4 0/4] ublk_drv: add generic mechanism to get/set parameters
Date: Mon, 1 Aug 2022 10:13:31 +0800 [thread overview]
Message-ID: <Yuc2yxnxoFVADcjX@T590> (raw)
In-Reply-To: <1596ad46-1a21-f7ac-a335-059b7d6732f5@kernel.dk>
On Sat, Jul 30, 2022 at 09:04:24AM -0600, Jens Axboe wrote:
> On 7/30/22 3:27 AM, Ming Lei wrote:
> > Hello Jens,
> >
> > The 1st two patches fixes ublk device leak or hang issue in case of some
> > failure path, such as, failing to start device.
> >
> > The 3rd patch adds two control commands for setting/getting device
> > parameters in generic way, and easy to extend to add new parameter
> > type.
> >
> > The 4th patch cleans UAPI of ublksrv_ctrl_dev_info, and userspace needs
> > to be updated for this driver change, so please consider this patchset
> > for v5.20.
> >
> > Verified by all targets in the following branch, and pass all built-in
> > tests.
>
> This will miss the first pull request, but I've queued it up for this
> merge window.
That is great, thanks for queuing it up!
--
Ming
next prev parent reply other threads:[~2022-08-01 2:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-30 9:27 [PATCH V4 0/4] ublk_drv: add generic mechanism to get/set parameters Ming Lei
2022-07-30 9:27 ` [PATCH V4 1/4] ublk_drv: cancel device even though disk isn't up Ming Lei
2022-07-30 9:27 ` [PATCH V4 2/4] ublk_drv: fix ublk device leak in case that add_disk fails Ming Lei
2022-07-30 9:27 ` [PATCH V4 3/4] ublk_drv: add SET_PARAMS/GET_PARAMS control command Ming Lei
2022-07-30 9:27 ` [PATCH V4 4/4] ublk_drv: cleanup ublksrv_ctrl_dev_info Ming Lei
2022-07-30 15:04 ` [PATCH V4 0/4] ublk_drv: add generic mechanism to get/set parameters Jens Axboe
2022-08-01 2:13 ` Ming Lei [this message]
2022-07-30 15:04 ` Jens Axboe
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=Yuc2yxnxoFVADcjX@T590 \
--to=ming.lei@redhat.com \
--cc=ZiyangZhang@linux.alibaba.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@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;
as well as URLs for NNTP newsgroup(s).