From: Peter Maydell <peter.maydell-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: Laszlo Ersek <lersek-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: QEMU Developers
<qemu-devel-qX2TKyscuCcdnm+yROfE0A@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
Subject: Re: [kernel PATCH v2 0/2] devicetree: document ARM bindings for QEMU's Firmware Config interface
Date: Thu, 4 Dec 2014 10:35:36 +0000 [thread overview]
Message-ID: <CAFEAcA-jXHCbi3o6h6fSu37WRB4684YTiAPUpoR9mU2iXc4EUQ@mail.gmail.com> (raw)
In-Reply-To: <1417366282-13527-1-git-send-email-lersek-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
On 30 November 2014 at 16:51, Laszlo Ersek <lersek-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> wrote:
> V2 seeks to address comments raised in the v1 review. Changes are broken
> out per patch, as git notes.
>
> Thanks
> Laszlo
>
> Laszlo Ersek (2):
> devicetree: document the "qemu" and "virtio" vendor prefixes
> devicetree: document ARM bindings for QEMU's Firmware Config interface
>
> Documentation/devicetree/bindings/arm/fw-cfg.txt | 57 ++++++++++++++++++++++
> .../devicetree/bindings/vendor-prefixes.txt | 2 +
> 2 files changed, 59 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/arm/fw-cfg.txt
If the device tree folks are happy with this binding then it
works for me on the QEMU side.
Acked-by: Peter Maydell <peter.maydell-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
-- PMM
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2014-12-04 10:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-30 16:51 [kernel PATCH v2 0/2] devicetree: document ARM bindings for QEMU's Firmware Config interface Laszlo Ersek
[not found] ` <1417366282-13527-1-git-send-email-lersek-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-11-30 16:51 ` [kernel PATCH v2 1/2] devicetree: document the "qemu" and "virtio" vendor prefixes Laszlo Ersek
2014-11-30 16:51 ` [kernel PATCH v2 2/2] devicetree: document ARM bindings for QEMU's Firmware Config interface Laszlo Ersek
[not found] ` <1417366282-13527-3-git-send-email-lersek-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-12-05 18:57 ` Peter Maydell
2014-12-05 19:04 ` Laszlo Ersek
[not found] ` <548201C0.1060006-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-12-05 19:08 ` Peter Maydell
[not found] ` <CAFEAcA8xvJMHKPQOdhH1+RF_MzKQaiqOT3uKF3OhrGSmHkzeRg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-12-10 14:44 ` Arnd Bergmann
2014-12-04 10:35 ` Peter Maydell [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=CAFEAcA-jXHCbi3o6h6fSu37WRB4684YTiAPUpoR9mU2iXc4EUQ@mail.gmail.com \
--to=peter.maydell-qsej5fyqhm4dnm+yrofe0a@public.gmane.org \
--cc=arnd-r2nGTMty4D4@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lersek-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=qemu-devel-qX2TKyscuCcdnm+yROfE0A@public.gmane.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).