qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org, Eric Blake <eblake@redhat.com>
Subject: Re: [PATCH for-9.0] qapi: drop unused QCryptoBlockCreateOptionsLUKS.detached-header
Date: Mon, 22 Jul 2024 14:01:20 +0100	[thread overview]
Message-ID: <Zp5YICB4dCjh3e-X@redhat.com> (raw)
In-Reply-To: <87jzlyyzo0.fsf@pond.sub.org>

On Tue, Mar 19, 2024 at 05:06:07PM +0100, Markus Armbruster wrote:
> Daniel P. Berrangé <berrange@redhat.com> writes:
> 
> > The 'detached-header' field in QCryptoBlockCreateOptionsLUKS
> > was left over from earlier patch iterations.
> >
> > Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> > ---
> >  qapi/crypto.json | 5 +----
> >  1 file changed, 1 insertion(+), 4 deletions(-)
> >
> > diff --git a/qapi/crypto.json b/qapi/crypto.json
> > index 931c88e688..ad9e3d0297 100644
> > --- a/qapi/crypto.json
> > +++ b/qapi/crypto.json
> > @@ -226,8 +226,6 @@
> >  # @iter-time: number of milliseconds to spend in PBKDF passphrase
> >  #     processing.  Currently defaults to 2000. (since 2.8)
> >  #
> > -# @detached-header: create a detached LUKS header. (since 9.0)
> > -#
> >  # Since: 2.6
> >  ##
> >  { 'struct': 'QCryptoBlockCreateOptionsLUKS',
> > @@ -237,8 +235,7 @@
> >              '*ivgen-alg': 'QCryptoIVGenAlgorithm',
> >              '*ivgen-hash-alg': 'QCryptoHashAlgorithm',
> >              '*hash-alg': 'QCryptoHashAlgorithm',
> > -            '*iter-time': 'int',
> > -            '*detached-header': 'bool'}}
> > +            '*iter-time': 'int' }}
> >  
> >  ##
> >  # @QCryptoBlockOpenOptions:
> 
> Glad you caught this in time.
> 
> Acked-by: Markus Armbruster <armbru@redhat.com>

Urgh, it appears this patch got lost and was not in fact included in
9.0.  What's your opinion on removing it from 9.1 with no deprecation
period ?  Functionally it did absolutely nothing even if used, so
removing it at most would cause an incorrect field to now be rejected.



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:[~2024-07-22 13:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-19 15:39 [PATCH for-9.0] qapi: drop unused QCryptoBlockCreateOptionsLUKS.detached-header Daniel P. Berrangé
2024-03-19 16:06 ` Markus Armbruster
2024-07-22 13:01   ` Daniel P. Berrangé [this message]
2024-07-22 14:07     ` Markus Armbruster
2024-07-22 14:14       ` Daniel P. Berrangé

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=Zp5YICB4dCjh3e-X@redhat.com \
    --to=berrange@redhat.com \
    --cc=armbru@redhat.com \
    --cc=eblake@redhat.com \
    --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).