All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: gjoyce@linux.vnet.ibm.com, linux-block@vger.kernel.org,
	jarkko@kernel.org
Cc: linuxppc-dev@lists.ozlabs.org, jonathan.derrick@linux.dev,
	brking@linux.vnet.ibm.com, msuchanek@suse.de, mpe@ellerman.id.au,
	nayna@linux.ibm.com, akpm@linux-foundation.org,
	keyrings@vger.kernel.org
Subject: Re: [PATCH v7 0/3 RESEND] generic and PowerPC SED Opal keystore
Date: Fri, 8 Sep 2023 12:38:07 -0600	[thread overview]
Message-ID: <e1910f8e-5bcd-4c1c-a751-e4a530282b6b@kernel.dk> (raw)
In-Reply-To: <20230908153056.3503975-1-gjoyce@linux.vnet.ibm.com>

On 9/8/23 9:30 AM, gjoyce@linux.vnet.ibm.com wrote:
> From: Greg Joyce <gjoyce@linux.vnet.ibm.com>
> 
> This patchset extends the capabilites incorporated into for-6.6/block
> (https://git.kernel.dk/cgit/linux/commit/?h=for-6.6/block&id=3bfeb61256643281ac4be5b8a57e9d9da3db4335) by allowing the SED Opal key to be seeded into
> the keyring from a secure permanent keystore.
> 
> It has gone through numerous rounds of review and all comments/suggetions
> have been addressed. The reviews have covered all relevant areas including
> reviews by block and keyring developers as well as the SED Opal
> maintainer. The last patchset submission has not solicited any responses
> in the six weeks since it was last distributed. The changes are
> generally useful and ready for inclusion.

Best time to resend is generally once the merge window is closed again,
as I won't start applying patches for the next release before that
happens. I'll try to remember to pick this one up for 6.7.

-- 
Jens Axboe


WARNING: multiple messages have this Message-ID (diff)
From: Jens Axboe <axboe@kernel.dk>
To: gjoyce@linux.vnet.ibm.com, linux-block@vger.kernel.org,
	jarkko@kernel.org
Cc: nayna@linux.ibm.com, keyrings@vger.kernel.org,
	jonathan.derrick@linux.dev, brking@linux.vnet.ibm.com,
	akpm@linux-foundation.org, msuchanek@suse.de,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v7 0/3 RESEND] generic and PowerPC SED Opal keystore
Date: Fri, 8 Sep 2023 12:38:07 -0600	[thread overview]
Message-ID: <e1910f8e-5bcd-4c1c-a751-e4a530282b6b@kernel.dk> (raw)
In-Reply-To: <20230908153056.3503975-1-gjoyce@linux.vnet.ibm.com>

On 9/8/23 9:30 AM, gjoyce@linux.vnet.ibm.com wrote:
> From: Greg Joyce <gjoyce@linux.vnet.ibm.com>
> 
> This patchset extends the capabilites incorporated into for-6.6/block
> (https://git.kernel.dk/cgit/linux/commit/?h=for-6.6/block&id=3bfeb61256643281ac4be5b8a57e9d9da3db4335) by allowing the SED Opal key to be seeded into
> the keyring from a secure permanent keystore.
> 
> It has gone through numerous rounds of review and all comments/suggetions
> have been addressed. The reviews have covered all relevant areas including
> reviews by block and keyring developers as well as the SED Opal
> maintainer. The last patchset submission has not solicited any responses
> in the six weeks since it was last distributed. The changes are
> generally useful and ready for inclusion.

Best time to resend is generally once the merge window is closed again,
as I won't start applying patches for the next release before that
happens. I'll try to remember to pick this one up for 6.7.

-- 
Jens Axboe


  parent reply	other threads:[~2023-09-08 18:40 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-08 15:30 [PATCH v7 0/3 RESEND] generic and PowerPC SED Opal keystore gjoyce
2023-09-08 15:30 ` gjoyce
2023-09-08 15:30 ` [PATCH v7 1/3 RESEND] block:sed-opal: " gjoyce
2023-09-08 15:30   ` gjoyce
2023-09-13 16:56   ` Nathan Chancellor
2023-09-13 16:56     ` Nathan Chancellor
2023-09-13 20:49     ` Nick Desaulniers
2023-09-13 20:49       ` Nick Desaulniers
2023-09-13 21:33       ` Nathan Chancellor
2023-09-13 21:33         ` Nathan Chancellor
2023-09-27 20:25       ` Greg Joyce
2023-09-27 20:25         ` Greg Joyce
2023-09-27 20:30         ` Nick Desaulniers
2023-09-27 20:30           ` Nick Desaulniers
2023-09-08 15:30 ` [PATCH v7 2/3 RESEND] block: sed-opal: keystore access for SED Opal keys gjoyce
2023-09-08 15:30   ` gjoyce
2023-09-08 15:30 ` [PATCH v7 3/3 RESEND] powerpc/pseries: PLPKS SED Opal keystore support gjoyce
2023-09-08 15:30   ` gjoyce
2023-09-13 18:59   ` Nathan Chancellor
2023-09-13 18:59     ` Nathan Chancellor
2023-09-13 19:15     ` Jens Axboe
2023-09-13 19:15       ` Jens Axboe
2023-09-27 16:26       ` Greg Joyce
2023-09-27 16:26         ` Greg Joyce
2023-09-14  4:13     ` Michael Ellerman
2023-09-14 10:34       ` Michal Suchánek
2023-09-14 10:34         ` Michal Suchánek
2023-09-14 11:58         ` Michael Ellerman
2023-09-14 11:58           ` Michael Ellerman
2023-09-08 18:38 ` Jens Axboe [this message]
2023-09-08 18:38   ` [PATCH v7 0/3 RESEND] generic and PowerPC SED Opal keystore Jens Axboe
2023-09-11 22:19 ` Jens Axboe
2023-09-11 22:19   ` Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2023-07-21 21:19 gjoyce
2023-07-21 21:19 ` gjoyce

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=e1910f8e-5bcd-4c1c-a751-e4a530282b6b@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=akpm@linux-foundation.org \
    --cc=brking@linux.vnet.ibm.com \
    --cc=gjoyce@linux.vnet.ibm.com \
    --cc=jarkko@kernel.org \
    --cc=jonathan.derrick@linux.dev \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=msuchanek@suse.de \
    --cc=nayna@linux.ibm.com \
    /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.