From: Hannes Reinecke <hare@suse.de>
To: Bart Van Assche <bvanassche@acm.org>,
Avri Altman <Avri.Altman@wdc.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>
Cc: Christoph Hellwig <hch@lst.de>, Ming Lei <ming.lei@redhat.com>,
John Garry <john.garry@huawei.com>,
Mike Christie <michael.christie@oracle.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 0/4] Remove procfs support
Date: Mon, 15 Aug 2022 07:55:57 +0200 [thread overview]
Message-ID: <68af1d0a-b8ff-9be4-e6ab-424945ac1891@suse.de> (raw)
In-Reply-To: <e71a33f6-0a65-561b-33b9-6772239c21df@acm.org>
On 8/14/22 16:27, Bart Van Assche wrote:
> On 8/14/22 05:54, Avri Altman wrote:
>>> The SCSI sysfs interface made the procfs interface superfluous. sysfs
>>> support
> >
>> Field application engineers are using #cat /proc/scsi/scsi to get the
>> devices's fw version - Rev: xxx
>> Where should they look for that now?
>
> Hi Avri,
>
> Please take a look at the output of the following command:
>
> find /sys -name inquiry | xargs grep -aH .
>
The canonical method would 'lsscsi'; _slightly_ more convenient :-)
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: Ivo Totev, Andrew
Myers, Andrew McDonald, Martje Boudien Moerman
next prev parent reply other threads:[~2022-08-15 5:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 20:45 [PATCH 0/4] Remove procfs support Bart Van Assche
2022-08-12 20:45 ` [PATCH 1/4] scsi: esas2r: Rename two functions and two variables Bart Van Assche
2022-08-12 20:45 ` [PATCH 2/4] scsi: esas2r: Remove procfs support Bart Van Assche
2022-08-12 20:45 ` [PATCH 3/4] scsi: core: " Bart Van Assche
2022-08-12 21:17 ` Douglas Gilbert
2022-08-12 21:46 ` Bart Van Assche
2022-08-12 20:45 ` [PATCH 4/4] scsi: core: Update a source code comment Bart Van Assche
2022-08-14 12:54 ` [PATCH 0/4] Remove procfs support Avri Altman
2022-08-14 14:27 ` Bart Van Assche
2022-08-14 21:07 ` Douglas Gilbert
2022-08-15 13:38 ` Bart Van Assche
2022-08-15 16:21 ` Douglas Gilbert
2022-08-16 14:36 ` Avri Altman
2022-08-15 5:55 ` Hannes Reinecke [this message]
2022-08-15 15:26 ` Ewan Milne
2022-08-15 16:25 ` 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=68af1d0a-b8ff-9be4-e6ab-424945ac1891@suse.de \
--to=hare@suse.de \
--cc=Avri.Altman@wdc.com \
--cc=bvanassche@acm.org \
--cc=hch@lst.de \
--cc=john.garry@huawei.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=michael.christie@oracle.com \
--cc=ming.lei@redhat.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