qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Or Ozeri <ORO@il.ibm.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"qemu-block@nongnu.org" <qemu-block@nongnu.org>,
	Danny Harnik <DANNYH@il.ibm.com>,
	"idryomov@gmail.com" <idryomov@gmail.com>
Subject: Re: [PATCH v3] block/rbd: Add support for layered encryption
Date: Thu, 17 Nov 2022 12:48:56 +0000	[thread overview]
Message-ID: <Y3YtuDXUxdQhq73r@redhat.com> (raw)
In-Reply-To: <MN2PR15MB3488DA644C772F708108977E8A069@MN2PR15MB3488.namprd15.prod.outlook.com>

On Thu, Nov 17, 2022 at 12:42:04PM +0000, Or Ozeri wrote:
> 
> 
> > -----Original Message-----
> > From: Daniel P. Berrangé <berrange@redhat.com>
> > Sent: 16 November 2022 13:15
> > To: Or Ozeri <ORO@il.ibm.com>; qemu-devel@nongnu.org; qemu-
> > block@nongnu.org; Danny Harnik <DANNYH@il.ibm.com>;
> > idryomov@gmail.com
> > Subject: [EXTERNAL] Re: [PATCH v3] block/rbd: Add support for layered
> > encryption
> > 
> > On Wed, Nov 16, 2022 at 10:23:52AM +0000, Daniel P. Berrangé wrote:
> > 
> > So with that precedent I guess it is ok to add 'luks-any'.
> > 
> 
> So is it OK to leave the "luks-any" changes to this commit?
> If not, is it ok to split this to 2 commits, in the same "patch-series"?

It is conceptually separate from the layered encryption so
should be a separate commit, in a series.

> BTW is there a possibility this will actually make it to 7.2?

QEMU is in freeze now, which means we only take bug fixes, not
new features, until 8.0 opens up after release. It is fine to
send patches, as the maintainer can queue them until the tree
opens.

With regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



      reply	other threads:[~2022-11-17 12:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-15 12:25 [PATCH v3] block/rbd: Add support for layered encryption Or Ozeri
2022-11-15 17:34 ` Ilya Dryomov
2022-11-15 17:46 ` Daniel P. Berrangé
2022-11-16  9:03   ` Or Ozeri
2022-11-16 10:23     ` Daniel P. Berrangé
2022-11-16 11:15       ` Daniel P. Berrangé
2022-11-16 17:02         ` Ilya Dryomov
2022-11-17 12:42         ` Or Ozeri
2022-11-17 12:48           ` Daniel P. Berrangé [this message]

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=Y3YtuDXUxdQhq73r@redhat.com \
    --to=berrange@redhat.com \
    --cc=DANNYH@il.ibm.com \
    --cc=ORO@il.ibm.com \
    --cc=idryomov@gmail.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.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).