From: David Hildenbrand <david@redhat.com>
To: Joel Upham <jupham125@gmail.com>
Cc: "Ani Sinha" <anisinha@redhat.com>,
"Anthony Perard" <anthony.perard@citrix.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Eduardo Habkost" <eduardo@habkost.net>,
"Igor Mammedov" <imammedo@redhat.com>,
"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Paul Durrant" <paul@xen.org>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Yanan Wang" <wangyanan55@huawei.com>,
"open list:X86 Xen CPUs" <xen-devel@lists.xenproject.org>,
qemu-devel@nongnu.org
Subject: Re: [PATCH v1 1/1] Q35 Support
Date: Wed, 21 Jun 2023 18:39:18 +0200 [thread overview]
Message-ID: <b13cbcd2-9963-e904-9870-15e911a9fe6e@redhat.com> (raw)
In-Reply-To: <CADPhr0kMXxj1SUQggcNQeXY4wSbLNN1-Amqxo3uGVeBMSJmn-g@mail.gmail.com>
On 21.06.23 18:35, Joel Upham wrote:
> Sorry, this was sent in error when I did the git send-email for the
> folder. This was before I broke each patch down (after looking at the
> Qemu submission guidance). This is my first time sending a patch in this
> way, so thanks for the understanding. This patch can be ignored, as they
> are all covered elsewhere.
We've all been there (messing with git send-email), no need to feel bad :)
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2023-06-21 16:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1687127946.git.jupham125@gmail.com>
2023-06-20 17:24 ` [PATCH v1 1/1] Q35 Support Joel Upham
2023-06-21 11:10 ` David Hildenbrand
2023-06-21 16:35 ` Joel Upham
2023-06-21 16:39 ` David Hildenbrand [this message]
2023-06-21 17:27 ` Bernhard Beschow
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=b13cbcd2-9963-e904-9870-15e911a9fe6e@redhat.com \
--to=david@redhat.com \
--cc=anisinha@redhat.com \
--cc=anthony.perard@citrix.com \
--cc=berrange@redhat.com \
--cc=eduardo@habkost.net \
--cc=imammedo@redhat.com \
--cc=jupham125@gmail.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=paul@xen.org \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=sstabellini@kernel.org \
--cc=wangyanan55@huawei.com \
--cc=xen-devel@lists.xenproject.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).