From: Scott Bauer <sbauer@plzdonthack.me>
To: Revanth Rajashekar <revanth.rajashekar@intel.com>
Cc: linux-block@vger.kernel.org,
Jonathan Derrick <jonathan.derrick@intel.com>,
Jonas Rabenstine <jonas.rabenstein@studium.uni-erlangen.de>,
David Kozub <zub@linux.fjfi.cvut.cz>,
Jens Axboe <axboe@kernel.dk>
Subject: Re: [PATCH v3 3/3] block: sed-opal: Introduce Opal Datastore UID
Date: Sun, 3 Nov 2019 19:18:18 -0500 [thread overview]
Message-ID: <20191104001818.GC12665@hacktheplanet> (raw)
In-Reply-To: <20191031161322.16624-4-revanth.rajashekar@intel.com>
On Thu, Oct 31, 2019 at 10:13:22AM -0600, Revanth Rajashekar wrote:
> This patch introduces Opal Datastore UID.
> The generic read/write table ioctl can use this UID
> to access the Opal Datastore.
>
> Reviewed-by: Jon Derrick <jonathan.derrick@intel.com>
> Signed-off-by: Revanth Rajashekar <revanth.rajashekar@intel.com>
This is fine
Reviewed-by: Scott Bauer <sbauer@plzdonthack.me>
next prev parent reply other threads:[~2019-11-04 0:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-31 16:13 [PATCH v3 0/3] block: sed-opal: Generic Read/Write Opal Tables Revanth Rajashekar
2019-10-31 16:13 ` [PATCH v3 1/3] block: sed-opal: Generalizing write data to any opal table Revanth Rajashekar
2019-11-03 23:52 ` Scott Bauer
2019-10-31 16:13 ` [PATCH v3 2/3] block: sed-opal: Add support to read/write opal tables generically Revanth Rajashekar
2019-11-04 0:15 ` Scott Bauer
2019-10-31 16:13 ` [PATCH v3 3/3] block: sed-opal: Introduce Opal Datastore UID Revanth Rajashekar
2019-11-04 0:18 ` Scott Bauer [this message]
2019-11-04 14:12 ` [PATCH v3 0/3] block: sed-opal: Generic Read/Write Opal Tables Jens Axboe
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=20191104001818.GC12665@hacktheplanet \
--to=sbauer@plzdonthack.me \
--cc=axboe@kernel.dk \
--cc=jonas.rabenstein@studium.uni-erlangen.de \
--cc=jonathan.derrick@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=revanth.rajashekar@intel.com \
--cc=zub@linux.fjfi.cvut.cz \
/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.