From: Laszlo Ersek <lersek-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
rob.herring-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
peter.maydell-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
mark.rutland-5wv7dgnIgG8@public.gmane.org,
arnd-r2nGTMty4D4@public.gmane.org,
drjones-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
lersek-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Subject: [PATCH v3 0/2] devicetree: document ARM bindings for QEMU's Firmware Config interface
Date: Thu, 11 Dec 2014 04:49:10 +0100 [thread overview]
Message-ID: <1418269752-31516-1-git-send-email-lersek@redhat.com> (raw)
Addressing v2 comments from Peter Maydell and Arnd Bergmann. Also
documenting the new 64-bit wide data register, and possibility for
future extensions. Changes are noted on each patch.
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 | 72 ++++++++++++++++++++++
.../devicetree/bindings/vendor-prefixes.txt | 2 +
2 files changed, 74 insertions(+)
create mode 100644 Documentation/devicetree/bindings/arm/fw-cfg.txt
--
1.8.3.1
--
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
next reply other threads:[~2014-12-11 3:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 3:49 Laszlo Ersek [this message]
[not found] ` <1418269752-31516-1-git-send-email-lersek-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-12-11 3:49 ` [PATCH v3 1/2] devicetree: document the "qemu" and "virtio" vendor prefixes Laszlo Ersek
2014-12-11 3:49 ` [PATCH v3 2/2] devicetree: document ARM bindings for QEMU's Firmware Config interface Laszlo Ersek
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=1418269752-31516-1-git-send-email-lersek@redhat.com \
--to=lersek-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=arnd-r2nGTMty4D4@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=drjones-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=peter.maydell-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=rob.herring-QSEj5FYQhm4dnm+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).