From: Christoph Hellwig <hch@lst.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jens Axboe <axboe@kernel.dk>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>,
Sebastian Ott <sebott@linux.vnet.ibm.com>
Subject: Re: linux-next: manual merge of the block tree with the s390 tree
Date: Tue, 13 Jun 2017 08:20:55 +0200 [thread overview]
Message-ID: <20170613062055.GA30813@lst.de> (raw)
In-Reply-To: <20170613130649.6bcede94@canb.auug.org.au>
Btw, scm_blk.c blk-mq conversion seems odd if not broken. It should
always call blk_mq_complete_request from scm_request_finish and
then pass the error to blk_mq_end_request frin
there.
It would be great if such major block driver changes were Cc'ed to
linux-block.
next prev parent reply other threads:[~2017-06-13 6:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-13 3:06 linux-next: manual merge of the block tree with the s390 tree Stephen Rothwell
2017-06-13 6:20 ` Christoph Hellwig [this message]
2017-06-13 6:28 ` Stephen Rothwell
2017-06-13 11:20 ` Sebastian Ott
-- strict thread matches above, loose matches on Subject: below --
2010-08-24 0:53 Stephen Rothwell
2010-08-24 7:13 ` Martin Schwidefsky
2010-08-24 8:17 ` 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=20170613062055.GA30813@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sebott@linux.vnet.ibm.com \
--cc=sfr@canb.auug.org.au \
/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).