[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v3] block/rbd: Add support for layered encryption
|
From: |
Daniel P . Berrangé |
|
Subject: |
Re: [PATCH v3] block/rbd: Add support for layered encryption |
|
Date: |
Thu, 17 Nov 2022 12:48:56 +0000 |
|
User-agent: |
Mutt/2.2.7 (2022-08-07) |
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 :|