From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@lst.de>
Cc: Damien.LeMoal@wdc.com, linux-block@vger.kernel.org, dm-devel@redhat.com
Subject: Re: a fix and two cleanups around blk_stack_limits
Date: Mon, 20 Jul 2020 10:56:23 -0600 [thread overview]
Message-ID: <dfe56cf2-db3d-3461-9834-be314f4080ef@kernel.dk> (raw)
In-Reply-To: <20200720061251.652457-1-hch@lst.de>
On 7/20/20 12:12 AM, 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.
We should probably make this against for-5.9/drivers instead, to avoid
an unnecessary conflict when merging.
--
Jens Axboe
next prev parent reply other threads:[~2020-07-20 16:56 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 ` a fix and two cleanups around blk_stack_limits Damien Le Moal
2020-07-20 16:56 ` Jens Axboe [this message]
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=dfe56cf2-db3d-3461-9834-be314f4080ef@kernel.dk \
--to=axboe@kernel.dk \
--cc=Damien.LeMoal@wdc.com \
--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 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.