From: Ulf Hansson <ulf.hansson@linaro.org>
To: Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>
Cc: linux-mmc <linux-mmc@vger.kernel.org>,
linux-block <linux-block@vger.kernel.org>
Subject: Re: convert the mmc driver to use blk_mq_alloc_disk
Date: Thu, 17 Jun 2021 11:58:20 +0200 [thread overview]
Message-ID: <CAPDyKFpAeUfMuXxbYE62Hjdjs==9zDZthvTDjBnrDd6v9iPGQQ@mail.gmail.com> (raw)
In-Reply-To: <20210616053934.880951-1-hch@lst.de>
+ Jens
On Wed, 16 Jun 2021 at 07:39, Christoph Hellwig <hch@lst.de> wrote:
>
> Hi Ulf,
>
> can you take a look at this series which converts the mmc driver to the
> new blk_mq_alloc_disk interface. It is based upon Jens' for-5.14/block
> or for-next trees.
I don't see any issues with queuing this via Jens' tree, as I have
only a few minor changes queued in my mmc tree that touch the
corresponding files. None of which should cause a merge conflict, I
think.
>
> Diffstat:
> block.c | 28 ++++------------------------
> queue.c | 23 ++++++++++-------------
> queue.h | 2 +-
> 3 files changed, 15 insertions(+), 38 deletions(-)
Kind regards
Uffe
next prev parent reply other threads:[~2021-06-17 9:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 5:39 convert the mmc driver to use blk_mq_alloc_disk Christoph Hellwig
2021-06-16 5:39 ` [PATCH 1/2] mmc: remove an extra blk_{get,put}_queue pair Christoph Hellwig
2021-06-17 9:55 ` Ulf Hansson
2021-06-16 5:39 ` [PATCH 2/2] mmc: switch to blk_mq_alloc_disk Christoph Hellwig
2021-06-17 9:55 ` Ulf Hansson
[not found] ` <CGME20210621062208eucas1p2949c830b948c3cf7b3d636c5c5746753@eucas1p2.samsung.com>
2021-06-21 6:22 ` Marek Szyprowski
2021-06-21 6:59 ` Christoph Hellwig
2021-06-21 7:53 ` Marek Szyprowski
2021-06-17 9:58 ` Ulf Hansson [this message]
2021-06-17 13:40 ` convert the mmc driver to use blk_mq_alloc_disk 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='CAPDyKFpAeUfMuXxbYE62Hjdjs==9zDZthvTDjBnrDd6v9iPGQQ@mail.gmail.com' \
--to=ulf.hansson@linaro.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-mmc@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).