From: Scott Bauer <sbauer@plzdonthack.me>
To: Jens Axboe <axboe@kernel.dk>
Cc: jonathan.derrick@intel.com,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"zub@linux.fjfi.cvut.cz" <zub@linux.fjfi.cvut.cz>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"jonas.rabenstein@studium.uni-erlangen.de"
<jonas.rabenstein@studium.uni-erlangen.de>
Subject: Re: [PATCH v2 0/3] block: sed-opal: add support for shadow MBR done flag and write
Date: Sat, 29 Jun 2019 12:28:35 -0400 [thread overview]
Message-ID: <20190629162835.GA21042@hacktheplanet> (raw)
In-Reply-To: <d3074ee1-0506-511d-c29c-44effb4eda97@kernel.dk>
On Sat, Jun 29, 2019 at 10:26:52AM -0600, Jens Axboe wrote:
> On 6/29/19 10:19 AM, Scott Bauer wrote:
> >
> > Hey Jens,
> >
> > Can you please stage these for 5.3 aswell?
>
> Yes, looks fine to me. But it conflicts with the psid revert in terms
> of ioctl numbering. You fine with me renumbering IOC_OPAL_MBR_DONE to:
>
> #define IOC_OPAL_MBR_DONE _IOW('p', 233, struct opal_mbr_done)
Sorry for the conflict. That's fine. I'll fix up userland tooling.
>
> --
> Jens Axboe
>
next prev parent reply other threads:[~2019-06-29 16:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 20:46 [PATCH v2 0/3] block: sed-opal: add support for shadow MBR done flag and write David Kozub
2019-05-21 20:46 ` [PATCH v2 1/3] block: sed-opal: add ioctl for done-mark of shadow mbr David Kozub
2019-05-21 20:46 ` [PATCH v2 2/3] block: sed-opal: ioctl for writing to " David Kozub
2019-05-21 20:46 ` [PATCH v2 3/3] block: sed-opal: check size of " David Kozub
2019-06-25 20:47 ` [PATCH v2 0/3] block: sed-opal: add support for shadow MBR done flag and write Derrick, Jonathan
2019-06-29 16:19 ` Scott Bauer
2019-06-29 16:26 ` Jens Axboe
2019-06-29 16:28 ` Scott Bauer [this message]
2019-06-29 16:35 ` Jens Axboe
2019-06-29 16:37 ` Scott Bauer
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=20190629162835.GA21042@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=linux-kernel@vger.kernel.org \
--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.