From: Hannes Reinecke <hare@suse.de>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>,
John Garry <john.garry@huawei.com>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Hannes Reinecke <hare@suse.com>, Christoph Hellwig <hch@lst.de>,
Bart Van Assche <bvanassche@acm.org>,
Arnd Bergmann <arnd@arndb.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: arm scsi drivers
Date: Fri, 27 Aug 2021 17:23:50 +0200 [thread overview]
Message-ID: <087d1fa0-8796-5b97-36fc-379498f53380@suse.de> (raw)
In-Reply-To: <20210827150938.GU22278@shell.armlinux.org.uk>
On 8/27/21 5:09 PM, Russell King (Oracle) wrote:
> I haven't, sorry.
>
> I have run 5.x kernels on the hardware, and do have a set of patches
> kicking around for the SCSI drivers that do some cleanups. It looks
> like the fixup is pretty simple from the links you've sent - using
> scsi_cmd_to_rq() to get the tag.
>
> That said, I think I may only had one SCSI drive that came anywhere
> close to supported tagged queuing, so I never put much effort into
> tagged command support. Both acornscsi and fas216 have it disabled
> for this reason, so it's probably easier just to rip the tag code
> out of these drivers.
>
That's what I figured, too.
And that's what my patches do, killing the tag support from arm drivers
which had them disabled since the dawn of git history.
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@suse.de +49 911 74053 688
SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg
HRB 36809 (AG Nürnberg), Geschäftsführer: Felix Imendörffer
next prev parent reply other threads:[~2021-08-27 15:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-20 17:37 John Garry
2021-08-27 14:55 ` John Garry
2021-08-27 15:09 ` Russell King (Oracle)
2021-08-27 15:23 ` Hannes Reinecke [this message]
2021-09-01 8:03 ` John Garry
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=087d1fa0-8796-5b97-36fc-379498f53380@suse.de \
--to=hare@suse.de \
--cc=arnd@arndb.de \
--cc=bvanassche@acm.org \
--cc=hare@suse.com \
--cc=hch@lst.de \
--cc=jejb@linux.ibm.com \
--cc=john.garry@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=martin.petersen@oracle.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
all inboxes | Powered by JetHome®