From: Igor Mammedov <imammedo@redhat.com>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: qemu-devel@nongnu.org, Laurent Vivier <lvivier@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
Thomas Huth <thuth@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>,
Ben Warren <ben@skyportsystems.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Shannon Zhao <shannon.zhaosl@gmail.com>,
qemu-arm@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH v4 7/8] hw: acpi: Export and share the ARM RSDP build
Date: Mon, 17 Dec 2018 16:25:47 +0100 [thread overview]
Message-ID: <20181217162547.696ce9de@Igors-MacBook-Pro.local> (raw)
In-Reply-To: <20181217140611.GC4456@caravaggio>
On Mon, 17 Dec 2018 15:06:11 +0100
Samuel Ortiz <sameo@linux.intel.com> wrote:
>
> From: Samuel Ortiz <sameo@linux.intel.com>
Subject should be
[Qemu-devel] [PATCH v5 7/8] hw: acpi: Export and share the ARM RSDP build
^^^
and without "Re: "
>
> Now that build_rsdp() supports building both legacy and current RSDP
> tables, we can move it to a generic folder (hw/acpi) and have the i386
> ACPI code reuse it in order to reduce code duplication.
>
> Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
> Reviewed-by: Igor Mammedov <imammedo@redhat.com>
> ---
>
> V4 -> V5:
> * Fixed the 16 bytes padding comment.
>
> ---
[...]
next prev parent reply other threads:[~2018-12-17 15:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-17 10:48 [Qemu-devel] [PATCH v4 0/8] hw: acpi: RSDP fixes and refactoring Samuel Ortiz
2018-12-17 10:48 ` [Qemu-devel] [PATCH v4 1/8] hw: acpi: The RSDP build API can return void Samuel Ortiz
2018-12-17 10:48 ` [Qemu-devel] [PATCH v4 2/8] hw: arm: acpi: Fix incorrect checksums in RSDP Samuel Ortiz
2018-12-17 10:48 ` [Qemu-devel] [PATCH v4 3/8] hw: i386: Use correct RSDT length for checksum Samuel Ortiz
2018-12-17 10:48 ` [Qemu-devel] [PATCH v4 4/8] hw: arm: Carry RSDP specific data through AcpiRsdpData Samuel Ortiz
2018-12-17 10:48 ` [Qemu-devel] [PATCH v4 5/8] hw: arm: Convert the RSDP build to the buid_append_foo() API Samuel Ortiz
2018-12-17 10:48 ` [Qemu-devel] [PATCH v4 6/8] hw: arm: Support both legacy and current RSDP build Samuel Ortiz
2018-12-17 10:48 ` [Qemu-devel] [PATCH v4 7/8] hw: acpi: Export and share the ARM " Samuel Ortiz
2018-12-17 12:20 ` Igor Mammedov
2018-12-17 13:49 ` Samuel Ortiz
2018-12-17 15:35 ` Igor Mammedov
2018-12-17 16:46 ` Samuel Ortiz
2018-12-17 23:04 ` Michael S. Tsirkin
2018-12-17 14:06 ` Samuel Ortiz
2018-12-17 15:25 ` Igor Mammedov [this message]
2018-12-17 15:32 ` Samuel Ortiz
2018-12-17 15:34 ` [Qemu-devel] [PATCH v5 " Samuel Ortiz
2018-12-17 15:45 ` Andrew Jones
2018-12-17 10:48 ` [Qemu-devel] [PATCH v4 8/8] hw: acpi: Remove AcpiRsdpDescriptor and fix tests Samuel Ortiz
2018-12-18 1:10 ` [Qemu-devel] [PATCH v4 0/8] hw: acpi: RSDP fixes and refactoring Michael S. Tsirkin
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=20181217162547.696ce9de@Igors-MacBook-Pro.local \
--to=imammedo@redhat.com \
--cc=ben@skyportsystems.com \
--cc=ehabkost@redhat.com \
--cc=lvivier@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=sameo@linux.intel.com \
--cc=shannon.zhaosl@gmail.com \
--cc=thuth@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).