From: Shawn Guo <shawnguo@kernel.org>
To: "Horia Geantă" <horia.geanta@nxp.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
Harninder Rai <harninder.rai@nxp.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Bhaskar U <bhaskar.upadhaya@nxp.com>,
Will Deacon <will.deacon@arm.com>,
Dan Douglass <dan.douglass@nxp.com>,
Rob Herring <robh+dt@kernel.org>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm64: dts: ls1012a: add crypto node
Date: Fri, 24 Mar 2017 15:34:23 +0800 [thread overview]
Message-ID: <20170324073420.GM30608@dragon> (raw)
In-Reply-To: <DB4PR04MB0847D837CB2762D5094720CB983E0@DB4PR04MB0847.eurprd04.prod.outlook.com>
On Fri, Mar 24, 2017 at 07:17:50AM +0000, Horia Geantă wrote:
> >> + sec_mon: sec_mon@1e90000 {
> >
> > Hyphen is more preferred to be used in node name than underscore.
> >
> This would imply changing the
> Documentation/devicetree/bindings/crypto/fsl-sec4.txt binding and
> dealing with all the consequences, which IIUC is probably not worth.
I do not care the bindings doc that much, since I'm not the maintainer
of it. What are the consequences specifically, if we use a better node
name in dts than bindings example?
Shawn
WARNING: multiple messages have this Message-ID (diff)
From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: dts: ls1012a: add crypto node
Date: Fri, 24 Mar 2017 15:34:23 +0800 [thread overview]
Message-ID: <20170324073420.GM30608@dragon> (raw)
In-Reply-To: <DB4PR04MB0847D837CB2762D5094720CB983E0@DB4PR04MB0847.eurprd04.prod.outlook.com>
On Fri, Mar 24, 2017 at 07:17:50AM +0000, Horia Geant? wrote:
> >> + sec_mon: sec_mon at 1e90000 {
> >
> > Hyphen is more preferred to be used in node name than underscore.
> >
> This would imply changing the
> Documentation/devicetree/bindings/crypto/fsl-sec4.txt binding and
> dealing with all the consequences, which IIUC is probably not worth.
I do not care the bindings doc that much, since I'm not the maintainer
of it. What are the consequences specifically, if we use a better node
name in dts than bindings example?
Shawn
next prev parent reply other threads:[~2017-03-24 7:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 12:29 [PATCH] arm64: dts: ls1012a: add crypto node Horia Geantă
2017-03-22 12:29 ` Horia Geantă
2017-03-24 1:56 ` Shawn Guo
2017-03-24 1:56 ` Shawn Guo
2017-03-24 7:17 ` Horia Geantă
2017-03-24 7:17 ` Horia Geantă
2017-03-24 7:34 ` Shawn Guo [this message]
2017-03-24 7:34 ` Shawn Guo
2017-03-24 8:29 ` Horia Geantă
2017-03-24 8:29 ` Horia Geantă
[not found] ` <DB4PR04MB0847E3EE8F7FAC11DD85FAA8983E0-tLF+feb1Bz4/w1fYxD+T089NdZoXdze2vxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2017-03-24 14:03 ` Shawn Guo
2017-03-24 14:03 ` Shawn Guo
2017-03-28 7:19 ` Horia Geantă
2017-03-28 7:19 ` Horia Geantă
2017-03-28 10:41 ` Shawn Guo
2017-03-28 10:41 ` Shawn Guo
2017-03-28 11:46 ` [PATCH v2] " Horia Geantă
2017-03-28 11:46 ` Horia Geantă
2017-03-29 3:04 ` Shawn Guo
2017-03-29 3:04 ` Shawn Guo
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=20170324073420.GM30608@dragon \
--to=shawnguo@kernel.org \
--cc=bhaskar.upadhaya@nxp.com \
--cc=catalin.marinas@arm.com \
--cc=dan.douglass@nxp.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=harninder.rai@nxp.com \
--cc=herbert@gondor.apana.org.au \
--cc=horia.geanta@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=will.deacon@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.