From: Richard Weinberger <richard@nod.at>
To: Jens Axboe <axboe@kernel.dk>, linux-block@vger.kernel.org
Cc: linux-mtd@lists.infradead.org, David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH 16/17] mtd_blkdevs: convert to blk-mq
Date: Thu, 11 Oct 2018 23:18:55 +0200 [thread overview]
Message-ID: <19488748.6iqVKhkDGp@blindfold> (raw)
In-Reply-To: <263ca89f-94e4-1238-e396-8fb0a0111f97@kernel.dk>
Jens,
Am Donnerstag, 11. Oktober 2018, 23:14:07 CEST schrieb Jens Axboe:
> On 10/11/18 3:03 PM, Richard Weinberger wrote:
> > Jens,
> >
> > On Thu, Oct 11, 2018 at 7:00 PM Jens Axboe <axboe@kernel.dk> wrote:
> >>
> >> Straight forward conversion, using an internal list to enable the
> >> driver to pull requests at will.
> >>
> >> Dynamically allocate the tag set to avoid having to pull in the
> >> block headers for blktrans.h, since various mtd drivers use
> >> block conflicting names for defines and functions.
> >
> > This explodes on my test system. :-/
>
> I think I see it, that was pretty stupid... Can you try with this one
> on top as well?
>
> diff --git a/drivers/mtd/mtd_blkdevs.c b/drivers/mtd/mtd_blkdevs.c
> index c26d692781af..e8f8fddce063 100644
> --- a/drivers/mtd/mtd_blkdevs.c
> +++ b/drivers/mtd/mtd_blkdevs.c
> @@ -187,8 +187,8 @@ static void mtd_blktrans_work(struct mtd_blktrans_dev *dev)
> mutex_unlock(&dev->lock);
>
> if (!blk_update_request(req, res, blk_rq_cur_bytes(req))) {
> - req = NULL;
> __blk_mq_end_request(req, res);
> + req = NULL;
Hehe. :-)
With this fix applied it works and passes my trivial test.
Thanks,
//richard
next prev parent reply other threads:[~2018-10-11 21:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181011165909.32615-1-axboe@kernel.dk>
2018-10-11 16:59 ` [PATCH 16/17] mtd_blkdevs: convert to blk-mq Jens Axboe
2018-10-11 21:03 ` Richard Weinberger
2018-10-11 21:14 ` Jens Axboe
2018-10-11 21:18 ` Richard Weinberger [this message]
2018-10-11 21:21 ` Jens Axboe
2018-10-11 21:31 ` Richard Weinberger
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=19488748.6iqVKhkDGp@blindfold \
--to=richard@nod.at \
--cc=axboe@kernel.dk \
--cc=dwmw2@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-mtd@lists.infradead.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