From: Bart Van Assche <bvanassche@acm.org>
To: dgilbert@interlog.com, 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>,
Hannes Reinecke <hare@suse.de>,
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 06:38:37 -0700 [thread overview]
Message-ID: <5b83ac46-9c69-6eba-c19d-5124a022e86a@acm.org> (raw)
In-Reply-To: <ce3ae6cc-bd66-6139-f503-adeee3884313@interlog.com>
On 8/14/22 14:07, Douglas Gilbert wrote:
> How about lsscsi ?
> # lsscsi
> [0:0:0:0] disk Linux scsi_debug 0191 /dev/sda
> [1:0:0:0] disk Linux scsi_debug 0191 /dev/sdb
> [2:0:0:0] disk Linux scsi_debug 0191 /dev/sdc
> [N:0:1:1] disk SKHynix_HFS512GDE9X081N__1
> /dev/nvme0n1
>
> I plan to add JSON output to lsscsi in the near future.
Hi Doug,
It was not clear to me whether or not Avri needs to retrieve the version
information on an Android system. Neither /proc/scsi nor lsscsi are
available on recent Android systems. I will see whether I can include
the sg3_utils package in Android.
Thanks,
Bart.
next prev parent reply other threads:[~2022-08-15 13:38 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 [this message]
2022-08-15 16:21 ` Douglas Gilbert
2022-08-16 14:36 ` Avri Altman
2022-08-15 5:55 ` Hannes Reinecke
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=5b83ac46-9c69-6eba-c19d-5124a022e86a@acm.org \
--to=bvanassche@acm.org \
--cc=Avri.Altman@wdc.com \
--cc=dgilbert@interlog.com \
--cc=hare@suse.de \
--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