From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Mike Christie <michael.christie@oracle.com>,
target-devel@vger.kernel.org,
Konstantin Shelekhin <k.shelekhin@yadro.com>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, linux@yadro.com
Subject: Re: [PATCH v2 0/2] target: Introduce dummy devices
Date: Tue, 13 Apr 2021 01:48:13 -0400 [thread overview]
Message-ID: <161828336217.27813.4442940540515306830.b4-ty@oracle.com> (raw)
In-Reply-To: <20210322200938.53300-1-k.shelekhin@yadro.com>
On Mon, 22 Mar 2021 23:09:36 +0300, Konstantin Shelekhin wrote:
> This patch series (inspired by SCST) adds support for the dummy devices
> via the new DUMMY flag of rd_mcp. The rationale behind the change is to
> give a user the ability to create conifgurable devices for LUN 0 with
> custom WWN values (like vendor, product or revision) as some tools like
> QConvergeGUI use LUN 0 to identify the whole storage.
>
> The advantage over simply creating a NULLIO rd_mcp device is that the
> DUMMY device will not be seen as a block device, hence less confusion
> for the system administrator.
>
> [...]
Applied to 5.13/scsi-queue, thanks!
[1/2] target: Add the DUMMY flag to rd_mcp
https://git.kernel.org/mkp/scsi/c/0aecfa662e43
[2/2] target: Make the virtual LUN 0 device dummy
https://git.kernel.org/mkp/scsi/c/1b5ad814af5e
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2021-04-13 5:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 20:09 [PATCH v2 0/2] target: Introduce dummy devices Konstantin Shelekhin
2021-03-22 20:09 ` [PATCH v2 1/2] target: Add the DUMMY flag to rd_mcp Konstantin Shelekhin
2021-03-22 20:09 ` [PATCH v2 2/2] target: Make the virtual LUN 0 device dummy Konstantin Shelekhin
2021-04-02 15:09 ` [PATCH v2 0/2] target: Introduce dummy devices michael.christie
2021-04-13 5:48 ` Martin K. Petersen [this message]
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=161828336217.27813.4442940540515306830.b4-ty@oracle.com \
--to=martin.petersen@oracle.com \
--cc=k.shelekhin@yadro.com \
--cc=linux-scsi@vger.kernel.org \
--cc=linux@yadro.com \
--cc=michael.christie@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.