From: Thomas Huth <thuth@redhat.com>
To: Ani Sinha <ani@anisinha.ca>, mst@redhat.com, qemu-devel@nongnu.org
Cc: Laurent Vivier <lvivier@redhat.com>,
Igor Mammedov <imammedo@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH v5] Add a comment in bios-tables-test.c to clarify the reason behind approach
Date: Mon, 12 Oct 2020 16:12:51 +0200 [thread overview]
Message-ID: <72e35a9d-21f4-095d-1ae9-9ed33842dd24@redhat.com> (raw)
In-Reply-To: <105B94CB-1345-49FB-B296-F5236E448BC3@anisinha.ca>
On 12/10/2020 16.07, Ani Sinha wrote:
> Request to queue this patch with the next pull.
I can take it via qtest-next in case Michael / Igor do not plan to send a
pull request any time soon.
Thomas
next prev parent reply other threads:[~2020-10-12 14:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 14:25 [PATCH v5] Add a comment in bios-tables-test.c to clarify the reason behind approach Ani Sinha
2020-10-12 14:07 ` Ani Sinha
2020-10-12 14:12 ` Thomas Huth [this message]
2020-10-15 11:28 ` Ani Sinha
2020-10-15 13:05 ` Michael S. Tsirkin
2020-10-15 13:58 ` Thomas Huth
2020-10-15 14:53 ` Ani Sinha
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=72e35a9d-21f4-095d-1ae9-9ed33842dd24@redhat.com \
--to=thuth@redhat.com \
--cc=ani@anisinha.ca \
--cc=imammedo@redhat.com \
--cc=lvivier@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@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).