From: Paul Walmsley <paul.walmsley@sifive.com>
To: Rob Herring <robh@kernel.org>
Cc: Paul Walmsley <paul.walmsley@sifive.com>,
devicetree@vger.kernel.org, Palmer Dabbelt <palmer@sifive.com>,
Megan Wachs <megan@sifive.com>,
Wesley Terpstra <wesley@sifive.com>,
Mark Rutland <mark.rutland@arm.com>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
paul@pwsan.com
Subject: Re: [PATCH] dt-bindings: sifive: describe sifive-blocks versioning
Date: Thu, 6 Dec 2018 16:45:58 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.21.9999.1812061645070.29609@viisi.sifive.com> (raw)
In-Reply-To: <20181207000104.GA10814@bogus>
On Thu, 6 Dec 2018, Rob Herring wrote:
> On Wed, Nov 21, 2018 at 05:06:56PM -0800, Paul Walmsley wrote:
> >
> > For IP blocks that are generated from the public, open-source
> > sifive-blocks repository, describe the version numbering policy
> > that its maintainers intend to use, upon request from Rob
> > Herring <robh@kernel.org>.
> >
> > Cc: Rob Herring <robh+dt@kernel.org>
> > Cc: Palmer Dabbelt <palmer@sifive.com>
> > Cc: Megan Wachs <megan@sifive.com>
> > Cc: Wesley Terpstra <wesley@sifive.com>
> > Cc: Mark Rutland <mark.rutland@arm.com>
> > Cc: devicetree@vger.kernel.org
> > Cc: linux-riscv@lists.infradead.org
> > Cc: linux-kernel@vger.kernel.org
> > Signed-off-by: Paul Walmsley <paul.walmsley@sifive.com>
> > Signed-off-by: Paul Walmsley <paul@pwsan.com>
> > ---
> >
> > Hi Rob, please let me know if this document works with your
> > requirements, or if some changes are needed. - Paul
>
> Looks pretty good to me.
>
> > .../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?
> > +
> > +An example is "sifive,uart0" from:
> > +
> > +https://github.com/sifive/sifive-blocks/blob/master/src/main/scala/devices/uart/UART.scala#L43
>
> That's nice, but will be out of date as soon as someone adds or removes
> a line above it. Can you point to a tagged version?
Will do
- Paul
next prev parent reply other threads:[~2018-12-07 0:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-22 1:06 Paul Walmsley
2018-11-22 1:33 ` Atish Patra
2018-11-26 19:02 ` Palmer Dabbelt
2018-12-06 2:30 ` Paul Walmsley
2018-11-26 19:02 ` Palmer Dabbelt
2018-12-07 0:01 ` Rob Herring
2018-12-07 0:45 ` Paul Walmsley [this message]
2018-12-07 13:55 ` Rob Herring
2018-12-07 14:31 ` Paul Walmsley
2018-12-07 15:19 ` Rob Herring
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=alpine.DEB.2.21.9999.1812061645070.29609@viisi.sifive.com \
--to=paul.walmsley@sifive.com \
--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@pwsan.com \
--cc=robh@kernel.org \
--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
all inboxes | Powered by JetHome®