From: Peter Xu <peterx@redhat.com>
To: Juan Quintela <quintela@redhat.com>
Cc: qemu-devel@nongnu.org, Leonardo Bras <leobras@redhat.com>
Subject: Re: [PATCH] migration: Fix duplicated included in meson.build
Date: Tue, 16 May 2023 11:50:17 -0400 [thread overview]
Message-ID: <ZGOmOccOq8oV8Uar@x1n> (raw)
In-Reply-To: <20230509170217.83246-1-quintela@redhat.com>
On Tue, May 09, 2023 at 07:02:17PM +0200, Juan Quintela wrote:
> This is the commint with the merge error (not in the submited patch).
>
> commit 52623f23b0d114837a0d6278180b3e3ae8947117
> Author: Lukas Straub <lukasstraub2@web.de>
> Date: Thu Apr 20 11:48:35 2023 +0200
>
> ram-compress.c: Make target independent
>
> Make ram-compress.c target independent.
>
> Fixes: 52623f23b0d114837a0d6278180b3e3ae8947117
> Signed-off-by: Juan Quintela <quintela@redhat.com>
Reviewed-by: Peter Xu <peterx@redhat.com>
--
Peter Xu
prev parent reply other threads:[~2023-05-16 15:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-09 17:02 [PATCH] migration: Fix duplicated included in meson.build Juan Quintela
2023-05-16 15:35 ` Daniel P. Berrangé
2023-05-16 15:50 ` 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=ZGOmOccOq8oV8Uar@x1n \
--to=peterx@redhat.com \
--cc=leobras@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/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).