From: Damien Le Moal <Damien.LeMoal@wdc.com>
To: Christoph Hellwig <hch@lst.de>, "axboe@kernel.dk" <axboe@kernel.dk>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"dm-devel@redhat.com" <dm-devel@redhat.com>
Subject: Re: a fix and two cleanups around blk_stack_limits
Date: Mon, 20 Jul 2020 08:13:25 +0000 [thread overview]
Message-ID: <CY4PR04MB3751242EF7AE2172A719F201E77B0@CY4PR04MB3751.namprd04.prod.outlook.com> (raw)
In-Reply-To: 20200720061251.652457-1-hch@lst.de
On 2020/07/20 15:13, Christoph Hellwig wrote:
> Hi Jens,
>
> this series ensures that the zoned device limitations are properly
> inherited in blk_stack_limits, and then cleanups up two rather
> pointless wrappers around it.
>
Tested with dm-linear, dm-crypt and dm-zoned multi device setup (from dm-5.9
tree). No problems detected.
Tested-by: Damien Le Moal <damien.lemoal@wdc.com>
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2020-07-20 8:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 6:12 a fix and two cleanups around blk_stack_limits Christoph Hellwig
2020-07-20 6:12 ` [PATCH 1/3] block: inherit the zoned characteristics in blk_stack_limits Christoph Hellwig
2020-07-20 6:45 ` Johannes Thumshirn
2020-07-20 8:09 ` Damien Le Moal
2020-07-21 17:32 ` Mike Snitzer
2020-07-20 6:12 ` [PATCH 2/3] block: remove bdev_stack_limits Christoph Hellwig
2020-07-20 8:11 ` Damien Le Moal
2020-07-20 8:15 ` Johannes Thumshirn
2020-07-20 6:12 ` [PATCH 3/3] block: remove blk_queue_stack_limits Christoph Hellwig
2020-07-20 8:11 ` Damien Le Moal
2020-07-20 8:16 ` Johannes Thumshirn
2020-07-20 8:13 ` Damien Le Moal [this message]
2020-07-20 16:56 ` a fix and two cleanups around blk_stack_limits Jens Axboe
2020-07-20 17:35 ` Christoph Hellwig
2020-07-20 21:35 ` Jens Axboe
2020-07-20 21:40 ` 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=CY4PR04MB3751242EF7AE2172A719F201E77B0@CY4PR04MB3751.namprd04.prod.outlook.com \
--to=damien.lemoal@wdc.com \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--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).