mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Garry <john.garry@huawei.com>
To: <linux@armlinux.org.uk>
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>
Subject: arm scsi drivers
Date: Fri, 20 Aug 2021 18:37:13 +0100	[thread overview]
Message-ID: <5a72842f-99db-8787-120b-6d85e7884e2d@huawei.com> (raw)

Hi Russell,

Recently we tried to remove scsi_cmnd.tags struct member [0].

However it now shows that some of the arm SCSI drivers continue to use 
this [1]. I think any other driver usage of this member had been found 
and removed.

The impression is that the usage of scsi_cmnd.tag in those drivers is 
quite dubious.

Now checking [2], it appears that you may have had some patches for 
these drivers locally.

So is that the case? Is this HW still used with bleeding edge kernels? 
If so, can we fix up this tag management?

[0] 
https://lore.kernel.org/linux-scsi/6c83bd7f-9fd2-1b43-627f-615467fa55d4@huawei.com/T/#mb47909f38f35837686734369600051b278d124af

[1] 
https://lore.kernel.org/linux-scsi/6c83bd7f-9fd2-1b43-627f-615467fa55d4@huawei.com/T/#md5d786e5753083b2f3e8e761b1c69809f82c7485

[2] 
https://lore.kernel.org/lkml/20210109174357.GB1551@shell.armlinux.org.uk/

Thanks,
John

             reply	other threads:[~2021-08-20 17:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-20 17:37 John Garry [this message]
2021-08-27 14:55 ` John Garry
2021-08-27 15:09   ` Russell King (Oracle)
2021-08-27 15:23     ` Hannes Reinecke
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=5a72842f-99db-8787-120b-6d85e7884e2d@huawei.com \
    --to=john.garry@huawei.com \
    --cc=arnd@arndb.de \
    --cc=bvanassche@acm.org \
    --cc=hare@suse.com \
    --cc=hch@lst.de \
    --cc=jejb@linux.ibm.com \
    --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®