From: Rob Herring <robh@kernel.org>
To: paul.walmsley@sifive.com
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, paul@pwsan.com, wesley@sifive.com,
palmer@sifive.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
megan@sifive.com, linux-riscv@lists.infradead.org
Subject: Re: [PATCH] dt-bindings: sifive: describe sifive-blocks versioning
Date: Fri, 7 Dec 2018 09:19:14 -0600 [thread overview]
Message-ID: <CABGGisyc-nLZkxtJAr5-BT4ziJO1AW6MU-4ChgBV73No67y0PA@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.9999.1812070624180.16511@viisi.sifive.com>
On Fri, Dec 7, 2018 at 8:31 AM Paul Walmsley <paul.walmsley@sifive.com> wrote:
>
>
> On Fri, 7 Dec 2018, Rob Herring wrote:
>
> > On Thu, Dec 6, 2018 at 6:46 PM Paul Walmsley <paul.walmsley@sifive.com> wrote:
> > > On Thu, 6 Dec 2018, Rob Herring wrote:
> > > > On Wed, Nov 21, 2018 at 05:06:56PM -0800, Paul Walmsley wrote:
> > > >
> > > > > .../sifive/sifive-blocks-ip-versioning.txt | 38 +++++++++++++++++++
> > > > > 1 file changed, 38 insertions(+)
> > > > > create mode 100644 Documentation/devicetree/bindings/sifive/sifive-blocks-ip-versioning.txt
> > > >
> > > > Use the path that was suggested.
> > >
> > > Could you remind me which one that is?
> >
> > In this thread: bindings/riscv/sifive/
>
> SiFive also produces ARM-based SoCs. Some of those ARM SoCs may use these
> IP blocks from sifive-blocks as well. As far as I know, there's nothing
> RISC-V-specific about most of these IP blocks. (As an example, there's
> nothing CPU architecture-specific about a UART.)
Fair enough. As-is is fine.
Rob
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2018-12-07 15:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-22 1:06 [PATCH] dt-bindings: sifive: describe sifive-blocks versioning Paul Walmsley
2018-11-22 1:06 ` Paul Walmsley
2018-11-22 1:33 ` Atish Patra
2018-11-22 1:33 ` Atish Patra
2018-11-26 19:02 ` Palmer Dabbelt
2018-11-26 19:02 ` Palmer Dabbelt
2018-12-06 2:30 ` Paul Walmsley
2018-11-26 19:02 ` Palmer Dabbelt
2018-11-26 19:02 ` Palmer Dabbelt
2018-12-07 0:01 ` Rob Herring
2018-12-07 0:45 ` Paul Walmsley
2018-12-07 13:55 ` Rob Herring
2018-12-07 14:31 ` Paul Walmsley
2018-12-07 15:19 ` Rob Herring [this message]
2019-05-13 20:47 ` Rob Herring
2019-05-13 21:07 ` Paul Walmsley
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=CABGGisyc-nLZkxtJAr5-BT4ziJO1AW6MU-4ChgBV73No67y0PA@mail.gmail.com \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=megan@sifive.com \
--cc=palmer@sifive.com \
--cc=paul.walmsley@sifive.com \
--cc=paul@pwsan.com \
--cc=wesley@sifive.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).