All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Bauer <sbauer@plzdonthack.me>
To: David Kozub <zub@linux.fjfi.cvut.cz>
Cc: linux-kernel@vger.kernel.org, hch@infradead.org,
	jonathan.derrick@intel.com, linux-block@vger.kernel.org
Subject: Re: [PATCH 00/16] block: sed-opal: support shadow MBR done flag and write
Date: Thu, 17 Jan 2019 16:13:52 -0500	[thread overview]
Message-ID: <20190117211306.GA29671@hacktheplanet> (raw)

On Wed, Jan 16, 2019 at 09:56:51PM +0000, David Kozub wrote:
>   block: sed-opal: rename next to execute_steps

I don't see this change anywhere on the lists. I have 0->15, but am missing 16/16.

Please resend v2 with the changes Christoph requested, so it's easier to review.

Lastly, please CC me on the changes, and I will review them:
sbauer@plzdonthack.me

I don't work at Intel anymore -- maintainers never got updated.


> Jonas Rabenstein (8):
>   block: sed-opal: use correct macro for method length
>   block: sed-opal: unify space check in add_token_*
>   block: sed-opal: print failed function address
>   block: sed-opal: split generation of bytestring header and content
>   block: sed-opal: add ioctl for done-mark of shadow mbr
>   block: sed-opal: ioctl for writing to shadow mbr
>   block: sed-opal: unify retrieval of table columns
>   block: sed-opal: check size of shadow mbr
> 
>  block/opal_proto.h            |  18 +
>  block/sed-opal.c              | 843 +++++++++++++++++-----------------
>  include/linux/sed-opal.h      |   2 +
>  include/uapi/linux/sed-opal.h |   9 +
>  4 files changed, 449 insertions(+), 423 deletions(-)
> 
> -- 
> 2.20.1

             reply	other threads:[~2019-01-17 22:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-17 21:13 Scott Bauer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-01-16 21:56 [PATCH 00/16] block: sed-opal: support shadow MBR done flag and write David Kozub
2019-01-17  8:57 ` Christoph Hellwig
2019-01-17  9:40   ` David Kozub
2019-01-17 15:22     ` Christoph Hellwig

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=20190117211306.GA29671@hacktheplanet \
    --to=sbauer@plzdonthack.me \
    --cc=hch@infradead.org \
    --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.