From: Peter Xu <peterx@redhat.com>
To: "Дмитрий Фролов" <frolov@swemel.ru>
Cc: Juan Quintela <quintela@redhat.com>,
Fabiano Rosas <farosas@suse.de>,
Leonardo Bras <leobras@redhat.com>,
qemu-devel@nongnu.org, sdl.qemu@linuxtesting.org
Subject: Re: [PATCH v1] migration: fix RAMBlock add NULL check
Date: Wed, 11 Oct 2023 10:24:55 -0400 [thread overview]
Message-ID: <ZSawNzXp523+/sDe@x1n> (raw)
In-Reply-To: <04093899-57e7-75bf-5b16-0ec08708a2d0@swemel.ru>
On Wed, Oct 11, 2023 at 04:20:42PM +0300, Дмитрий Фролов wrote:
> I do not insist on accepting this patch - it is more like RFC.
> Also, i can add more verbose message and assert, if necessary.
That's totally fine. It's just that then we should drop the Fixes line
above because it doesn't need to be backported to stable.
Also feel free to add more verbose print message or assert if you're
posting a new version.
Thanks,
--
Peter Xu
next prev parent reply other threads:[~2023-10-11 14:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 10:48 [PATCH v1] migration: fix RAMBlock add NULL check Dmitry Frolov
2023-10-10 13:36 ` Fabiano Rosas
2023-10-10 19:23 ` Peter Xu
2023-10-11 13:20 ` Дмитрий Фролов
2023-10-11 14:24 ` Peter Xu [this message]
2023-10-11 14:33 ` Juan Quintela
2023-10-11 14:36 ` Дмитрий Фролов
2023-10-11 13:07 ` Juan Quintela
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=ZSawNzXp523+/sDe@x1n \
--to=peterx@redhat.com \
--cc=farosas@suse.de \
--cc=frolov@swemel.ru \
--cc=leobras@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=sdl.qemu@linuxtesting.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.