From: Markus Armbruster <armbru@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>,
Peter Xu <peterx@redhat.com>
Subject: Re: [PATCH for-6.0] migration: Drop redundant query-migrate result @blocked
Date: Tue, 20 Apr 2021 06:27:12 +0200 [thread overview]
Message-ID: <87tuo1shr3.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <YH29K3Wa/gyceh72@work-vm> (David Alan Gilbert's message of "Mon, 19 Apr 2021 18:26:03 +0100")
"Dr. David Alan Gilbert" <dgilbert@redhat.com> writes:
> * Peter Maydell (peter.maydell@linaro.org) wrote:
>> On Mon, 19 Apr 2021 at 17:27, Markus Armbruster <armbru@redhat.com> wrote:
>> >
>> > Result @blocked is true when and only when result @blocked-reasons is
>> > present. It's always non-empty when present. @blocked is redundant;
>> > drop.
>> >
>> > Signed-off-by: Markus Armbruster <armbru@redhat.com>
>
> So I'm OK with it in principal and I think the code is OK, so
>
> Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
>
>> "for-6.0" needs to be accompanied by a justification of why it's
>> important to go in the release at this point...
You're right. My bad.
> I guess the argument is that when we hit 6.0 it becomes API and removing
> the 'blocked' becomes a matter of deprecation which is a pain.
Correct.
> Hmm; I agree it's the right change, but I'm not sure I can justify it
> this late in the release.
If we decide taking it out is too late, we should at least deprecate it
in 6.0. I'll post the patch, so you guys can pick the one you like
better.
prev parent reply other threads:[~2021-04-20 4:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-19 16:27 [PATCH for-6.0] migration: Drop redundant query-migrate result @blocked Markus Armbruster
2021-04-19 16:32 ` Peter Maydell
2021-04-19 17:26 ` Dr. David Alan Gilbert
2021-04-20 4:27 ` Markus Armbruster [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=87tuo1shr3.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=peterx@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 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.