All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>,
	stefanb@linux.vnet.ibm.com
Cc: stefanb@linux.vnet.ibm.com, farosas@suse.de,
	qemu-devel@nongnu.org, armbru@redhat.com, berrange@redhat.com,
	armenon@redhat.com
Subject: Re: [PATCH v4 0/2] migration: vmsd errp handlers: return bool
Date: Thu, 30 Oct 2025 16:27:17 -0400	[thread overview]
Message-ID: <aQPKJSj0nERfKTKS@x1.local> (raw)
In-Reply-To: <20251028130738.29037-1-vsementsov@yandex-team.ru>

On Tue, Oct 28, 2025 at 04:07:36PM +0300, Vladimir Sementsov-Ogievskiy wrote:
> Hi.
> 
> Finally, I understood, that there is no real benefit in converting
> these new APIs to bool, as it will break plans of converting all
> other handlers to new API.
> 
> So, only unrelated fixes are kept in the series, maintainers may
> pick them in separate if convenient.
> 
> v4:
> 01: add r-b by Stefan
> 02: rework to better patch (and fix one more similar issue)

Stefan, are you ok on patch 2?

If no objections, I can pick this up for 10.2.

Thanks,

-- 
Peter Xu



      parent reply	other threads:[~2025-10-30 20:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-28 13:07 [PATCH v4 0/2] migration: vmsd errp handlers: return bool Vladimir Sementsov-Ogievskiy
2025-10-28 13:07 ` [PATCH v4 1/2] migration: vmstate_save_state_v(): fix error path Vladimir Sementsov-Ogievskiy
2025-10-28 13:07 ` [PATCH v4 2/2] tmp_emulator: improve and fix use of errp Vladimir Sementsov-Ogievskiy
2025-10-31 19:45   ` Stefan Berger
2025-11-06 12:29   ` Markus Armbruster
2025-11-06 12:57     ` Vladimir Sementsov-Ogievskiy
2025-10-28 17:09 ` [PATCH v4 3/4] migration/vmstate: stop reporting error number for new _errp APIs Vladimir Sementsov-Ogievskiy
2025-10-28 17:09   ` [PATCH v4 4/4] migration: vmsd errp handlers: return bool Vladimir Sementsov-Ogievskiy
2025-10-28 17:12 ` [PATCH v4 0/2] " Vladimir Sementsov-Ogievskiy
2025-10-30 20:27 ` Peter Xu [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=aQPKJSj0nERfKTKS@x1.local \
    --to=peterx@redhat.com \
    --cc=armbru@redhat.com \
    --cc=armenon@redhat.com \
    --cc=berrange@redhat.com \
    --cc=farosas@suse.de \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanb@linux.vnet.ibm.com \
    --cc=vsementsov@yandex-team.ru \
    /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.