From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Dmitry Bogdanov <d.bogdanov@yadro.com>
Cc: Martin Petersen <martin.petersen@oracle.com>,
<target-devel@vger.kernel.org>,
Mike Christie <michael.christie@oracle.com>,
<linux-scsi@vger.kernel.org>, <linux@yadro.com>
Subject: Re: [PATCH v2 0/6] add support of RSOC command
Date: Wed, 26 Oct 2022 22:14:29 -0400 [thread overview]
Message-ID: <yq1zgdirp1o.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20220906103421.22348-1-d.bogdanov@yadro.com> (Dmitry Bogdanov's message of "Tue, 6 Sep 2022 13:34:15 +0300")
Dmitry,
> The patchset adds support of REPORT SUPPORTED OPERATION CODES command
> according to SPC4. Including CDB USAGE DATA and timeout descriptors.
> Timeout descriptors are zeroed currently, meaning that no time is
> indicated, but an encoding of it there is. Opcode support and Usage
> Data are dynamically generated - reflects the backstore configuration.
> libiscsi tests for RSOC and tests that uses RSOC command are all
> PASSED.
Applied to 6.2/scsi-staging, thanks!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2022-10-27 2:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 10:34 [PATCH v2 0/6] add support of RSOC command Dmitry Bogdanov
2022-09-06 10:34 ` [PATCH v2 1/6] scsi: target: core: " Dmitry Bogdanov
2022-09-06 10:34 ` [PATCH v2 2/6] scsi: target: core: add list of opcodes for RSOC Dmitry Bogdanov
2022-09-06 10:34 ` [PATCH v2 3/6] scsi: target: core: dynamic opcode support in RSOC Dmitry Bogdanov
2022-09-06 10:34 ` [PATCH v2 4/6] scsi: target: core: add emulate_rsoc attribute Dmitry Bogdanov
2022-09-06 10:34 ` [PATCH v2 5/6] scsi: target: check emulate_3pc for RECEIVE COPY Dmitry Bogdanov
2022-09-06 10:34 ` [PATCH v2 6/6] scsi: target: core: dynamicaly set dpofua in usage_bits Dmitry Bogdanov
2022-09-29 20:34 ` [PATCH v2 0/6] add support of RSOC command Mike Christie
2022-10-27 2:14 ` Martin K. Petersen [this message]
2022-11-08 4:01 ` Martin K. Petersen
-- strict thread matches above, loose matches on Subject: below --
2022-08-15 7:17 Dmitry Bogdanov
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=yq1zgdirp1o.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=d.bogdanov@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).