From: Steffen Maier <maier@linux.ibm.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>,
Ming Lei <tom.leiming@gmail.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Mark Brown <broonie@kernel.org>
Cc: "James E . J . Bottomley" <jejb@linux.ibm.com>,
Ming Lei <ming.lei@redhat.com>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux SCSI List <linux-scsi@vger.kernel.org>,
linux-block <linux-block@vger.kernel.org>,
"open list:DEVICE-MAPPER (LVM)" <dm-devel@redhat.com>,
linux-s390 <linux-s390@vger.kernel.org>,
Benjamin Block <bblock@linux.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Bart Van Assche <bvanassche@acm.org>,
Hannes Reinecke <hare@suse.com>, Jens Axboe <axboe@kernel.dk>,
"Ewan D . Milne" <emilne@redhat.com>,
Christoph Hellwig <hch@lst.de>, Mike Snitzer <snitzer@redhat.com>
Subject: Re: [PATCH 1/2] scsi: core: fix missing .cleanup_rq for SCSI hosts without request batching
Date: Wed, 18 Sep 2019 17:09:50 +0200 [thread overview]
Message-ID: <bec80a65-9a8c-54a9-fe70-876fcbe3d592@linux.ibm.com> (raw)
In-Reply-To: <yq136iccsbw.fsf@oracle.com>
On 8/8/19 4:18 AM, Martin K. Petersen wrote:
>
> Ming,
>
>>> + .cleanup_rq = scsi_cleanup_rq,
>>> .busy = scsi_mq_lld_busy,
>>> .map_queues = scsi_map_queues,
>>> };
>>
>> This one is a cross-tree thing, either scsi/5.4/scsi-queue needs to
>> pull for-5.4/block, or do it after both land linus tree.
>
> I'll set up an amalgamated for-next branch tomorrow.
Martin, is it possible that you re-wrote your for-next and it now no longer
contains a merged 5.4/scsi-postmerge with those fixes?
At least I cannot find the fix code in next-20190917 and it fails again for me.
--
Mit freundlichen Gruessen / Kind regards
Steffen Maier
Linux on IBM Z Development
https://www.ibm.com/privacy/us/en/
IBM Deutschland Research & Development GmbH
Vorsitzender des Aufsichtsrats: Matthias Hartmann
Geschaeftsfuehrung: Dirk Wittkopp
Sitz der Gesellschaft: Boeblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294
next prev parent reply other threads:[~2019-09-18 15:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-07 14:49 [PATCH 0/2] scsi: core: regression fixes for request batching Steffen Maier
2019-08-07 14:49 ` [PATCH 1/2] scsi: core: fix missing .cleanup_rq for SCSI hosts without " Steffen Maier
2019-08-07 23:32 ` Ming Lei
2019-08-08 2:18 ` Martin K. Petersen
2019-09-18 15:09 ` Steffen Maier [this message]
2019-09-18 15:22 ` Martin K. Petersen
2019-09-18 15:32 ` Mark Brown
2019-08-08 5:52 ` kbuild test robot
2019-08-09 1:56 ` kbuild test robot
2019-08-07 14:49 ` [PATCH 2/2] scsi: core: fix dh and multipathing " Steffen Maier
2019-08-08 6:02 ` kbuild test robot
2019-08-09 9:08 ` kbuild test robot
2019-08-07 16:17 ` [PATCH 0/2] scsi: core: regression fixes for " Paolo Bonzini
2019-08-07 17:08 ` Bart Van Assche
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=bec80a65-9a8c-54a9-fe70-876fcbe3d592@linux.ibm.com \
--to=maier@linux.ibm.com \
--cc=axboe@kernel.dk \
--cc=bblock@linux.ibm.com \
--cc=broonie@kernel.org \
--cc=bvanassche@acm.org \
--cc=dm-devel@redhat.com \
--cc=emilne@redhat.com \
--cc=gor@linux.ibm.com \
--cc=hare@suse.com \
--cc=hch@lst.de \
--cc=heiko.carstens@de.ibm.com \
--cc=jejb@linux.ibm.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=ming.lei@redhat.com \
--cc=pbonzini@redhat.com \
--cc=snitzer@redhat.com \
--cc=tom.leiming@gmail.com \
/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).