From: "Michael S. Tsirkin" <mst@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: peter.maydell@linaro.org, ehabkost@redhat.com,
ard.biesheuvel@linaro.org, matt@codeblueprint.co.uk,
stefanha@gmail.com, "Gabriel L. Somlo" <somlo@cmu.edu>,
qemu-devel@nongnu.org, leif.lindholm@linaro.org,
luto@amacapital.net, qemu-arm@nongnu.org, pbonzini@redhat.com,
Igor Mammedov <imammedo@redhat.com>,
lersek@redhat.com, rth@twiddle.net
Subject: Re: [Qemu-arm] [Qemu-devel] [PATCH v9 0/5] add ACPI node for fw_cfg on pc and arm
Date: Tue, 23 Feb 2016 11:53:47 +0200 [thread overview]
Message-ID: <20160223115206-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <1456217512.29896.78.camel@redhat.com>
On Tue, Feb 23, 2016 at 09:51:52AM +0100, Gerd Hoffmann wrote:
> On Mo, 2016-02-22 at 13:30 +0100, Igor Mammedov wrote:
> > On Fri, 19 Feb 2016 13:20:24 -0500
> > "Gabriel L. Somlo" <somlo@cmu.edu> wrote:
> >
> > Gerd,
> >
> > if you are going to apply it, you'll need to update
> > expected tables for acpi test (rebuild-expected-aml.sh)
> > as a commit on top of this series.
>
> Sure?
>
> Applied the series, ran "make check", no errors.
>
> cheers,
> Gerd
It's a warning not an error because of all the false positives it causes.
This is mostly an ACPI patchset, so my tree seems more
appropriate, but in case you prefer your tree,
I sent a Reviewed-by: Michael S. Tsirkin <mst@redhat.com>.
In that case please do update the expected tables.
--
MST
prev parent reply other threads:[~2016-02-23 9:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-19 18:20 [Qemu-arm] [PATCH v9 0/5] add ACPI node for fw_cfg on pc and arm Gabriel L. Somlo
2016-02-19 18:20 ` [Qemu-arm] [PATCH v9 1/5] fw_cfg: expose control register size in fw_cfg.h Gabriel L. Somlo
2016-02-19 18:20 ` [Qemu-arm] [PATCH v9 2/5] pc: fw_cfg: move ioport base constant to pc.h Gabriel L. Somlo
2016-02-19 18:20 ` [Qemu-arm] [PATCH v9 3/5] acpi: pc: add fw_cfg device node to dsdt Gabriel L. Somlo
2016-02-22 12:26 ` [Qemu-arm] [Qemu-devel] " Igor Mammedov
2016-02-23 9:51 ` [Qemu-arm] " Michael S. Tsirkin
2016-02-19 18:20 ` [Qemu-arm] [PATCH v9 4/5] acpi: arm: " Gabriel L. Somlo
2016-02-20 13:02 ` [Qemu-arm] [Qemu-devel] " Shannon Zhao
2016-02-23 9:51 ` [Qemu-arm] " Michael S. Tsirkin
2016-02-19 18:20 ` [Qemu-arm] [PATCH v9 5/5] fw_cfg: document ACPI device node information Gabriel L. Somlo
2016-02-23 9:51 ` Michael S. Tsirkin
2016-02-22 12:30 ` [Qemu-arm] [Qemu-devel] [PATCH v9 0/5] add ACPI node for fw_cfg on pc and arm Igor Mammedov
2016-02-23 8:51 ` Gerd Hoffmann
2016-02-23 9:48 ` Igor Mammedov
2016-02-23 10:39 ` Gerd Hoffmann
2016-02-23 10:56 ` Michael S. Tsirkin
2016-02-23 15:52 ` Igor Mammedov
2016-02-23 15:54 ` Michael S. Tsirkin
2016-02-23 16:25 ` Igor Mammedov
2016-02-23 9:53 ` Michael S. Tsirkin [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=20160223115206-mutt-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=ard.biesheuvel@linaro.org \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=kraxel@redhat.com \
--cc=leif.lindholm@linaro.org \
--cc=lersek@redhat.com \
--cc=luto@amacapital.net \
--cc=matt@codeblueprint.co.uk \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=somlo@cmu.edu \
--cc=stefanha@gmail.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).