From: Palmer Dabbelt <palmer@dabbelt.com>
To: tglx@linutronix.de
To: jason@lakedaemon.net
To: marc.zyngier@arm.com
To: robh+dt@kernel.org
To: mark.rutland@arm.com
To: jic23@kernel.org
To: treding@nvidia.com
To: maxime.ripard@free-electrons.com
To: marek.vasut@gmail.com
To: ccc94453@vip.cybercity.dk
To: gregkh@linuxfoundation.org
To: linux-kernel@vger.kernel.org
To: devicetree@vger.kernel.org
Subject: RISC-V Device Tree Documentation
Date: Mon, 26 Jun 2017 22:21:21 -0700 [thread overview]
Message-ID: <20170627052124.426-1-palmer@dabbelt.com> (raw)
As part of submitting the RISC-V Linux port it was suggested that we write some
documentation that describes our device tree bindings. Our port is still in
progress, but it was suggested that we start sending patches to the relevant
parties. There is one outstanding issue to resolve with the PLIC bindings, but
I think the other two patches should be sane.
next reply other threads:[~2017-06-27 5:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-27 5:21 Palmer Dabbelt [this message]
2017-06-27 5:21 ` [PATCH 1/3] dts: RISC-V vendor prefix Palmer Dabbelt
2017-06-29 20:35 ` Rob Herring
2017-06-29 23:45 ` Palmer Dabbelt
2017-06-27 5:21 ` [PATCH 2/3] dts: RISC-V local interrupt controller docs Palmer Dabbelt
2017-06-29 20:30 ` Rob Herring
2017-07-04 11:18 ` Mark Rutland
2017-06-27 5:21 ` [PATCH 3/3] dts: RISC-V PLIC documentation Palmer Dabbelt
2017-06-29 21:14 ` Rob Herring
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=20170627052124.426-1-palmer@dabbelt.com \
--to=palmer@dabbelt.com \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®