Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: John Garry <john.g.garry@oracle.com>
To: Gulam Mohamed <gulam.mohamed@oracle.com>,
	martin.petersen@oracle.com, linux-scsi@vger.kernel.org,
	target-devel@vger.kernel.org
Subject: Re: [PATCH V3 6.19/scsi-queue] scsi: target: core: Add emulation for REPORT_IDENTIFYING_INFORMATION
Date: Mon, 1 Dec 2025 11:18:02 +0000	[thread overview]
Message-ID: <5f51e632-494a-4ed7-b352-644552224b90@oracle.com> (raw)
In-Reply-To: <20251201110716.227588-1-gulam.mohamed@oracle.com>

On 01/12/2025 11:07, Gulam Mohamed wrote:
> Add the emulation for REPORT_IDENTIFYING_INFORMATION command using the
> configfs file pd_text_id_info in target core module. The configfs file is
> created in /sys/kernel/config/target/core/<backend type>/
> <backing_store_name>/wwn/. The user can set the peripheral device text
> identification string to the file pd_text_id_info. An emulation function
> "spc_emulate_report_id_info()" is defined in target_core_spc.c which
> returns the device text id whenever the user requests the same.
> 
> The details of the REPORT_IDENTIFYING_INFORMATION command is mentioned
> in the section 6.32 of spc4r37 specification document of SCSI Primary
> Commands.
> 
> Signed-off-by: Gulam Mohamed <gulam.mohamed@oracle.com>

thanks for doing an update

Reviewed-by: John Garry <john.g.garry@oracle.com>

BTW, if you do the changes according to the recommendation and those 
changes are straightforward, then you should add the RB tag granted.



  reply	other threads:[~2025-12-01 11:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-01 11:07 [PATCH V3 6.19/scsi-queue] scsi: target: core: Add emulation for REPORT_IDENTIFYING_INFORMATION Gulam Mohamed
2025-12-01 11:18 ` John Garry [this message]
2025-12-17  2:08 ` Martin K. Petersen
2025-12-17 21:06   ` Gulam Mohamed
2026-01-04 21:43 ` Martin K. Petersen

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=5f51e632-494a-4ed7-b352-644552224b90@oracle.com \
    --to=john.g.garry@oracle.com \
    --cc=gulam.mohamed@oracle.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=target-devel@vger.kernel.org \
    /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