From: Romain Perier <romain.perier@gmail.com>
To: Daniel Palmer <daniel@0x0f.com>
Cc: Rob Herring <robh+dt@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Olof Johansson <olof@lixom.net>, SoC Team <soc@kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
DTML <devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/4] dt-bindings: add vendor prefix for Wireless Tag
Date: Sat, 11 Sep 2021 14:20:58 +0200 [thread overview]
Message-ID: <CABgxDo+9WnjE5pu=ijN01htLucFYko--w2fJ+ZVazBg_cSLZ1w@mail.gmail.com> (raw)
In-Reply-To: <CAFr9PXmwRDfXmDR9UOGoQ2+_LDaSGgmg7n=Ek4RtBdiC2kfuLA@mail.gmail.com>
Hi Daniel,
Le sam. 11 sept. 2021 à 04:59, Daniel Palmer <daniel@0x0f.com> a écrit :
>
> Hi Romain,
> Sorry for sending this again. Gmail decided to switch to html email so
> the first version bounced from the mailing lists.
>
> On Sat, 11 Sept 2021 at 04:03, Romain Perier <romain.perier@gmail.com> wrote:
> >
> > This adds a vendor prefix for wireless tag boards and SOMs.
> >
> > Signed-off-by: Romain Perier <romain.perier@gmail.com>
> > ---
> > Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/vendor-prefixes.yaml b/Documentation/devicetree/bindings/vendor-prefixes.yaml
> > index a867f7102c35..b50d62dde7c5 100644
> > --- a/Documentation/devicetree/bindings/vendor-prefixes.yaml
> > +++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml
> > @@ -517,6 +517,8 @@ patternProperties:
> > description: International Business Machines (IBM)
> > "^icplus,.*":
> > description: IC Plus Corp.
> > + "^wirelesstag,.*":
> > + description: Wireless Tag (qiming yunduan)
> > "^idt,.*":
> > description: Integrated Device Technologies, Inc.
> > "^ifi,.*":
> > --
> > 2.33.0
> >
>
> This should be in alphabetical order.
> Also, this commit should be before adding the DT for the board I think.
> The prefix should be in before something that uses it.
>
> Thanks,
Ack, I will fix it.
Cheers,
Romain
next prev parent reply other threads:[~2021-09-11 12:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-10 19:03 [PATCH 0/4] Add support for IDO-SBC2D06-V1B-22W Romain Perier
2021-09-10 19:03 ` [PATCH 1/4] ARM: mstar: Mark timer with arm,cpu-registers-not-fw-configured Romain Perier
2021-09-10 19:03 ` [PATCH 2/4] ARM: dts: mstar: Add the Wireless Tag IDO-SBC2D06-V1B-22W Romain Perier
2021-09-11 3:18 ` Daniel Palmer
2021-09-11 12:19 ` Romain Perier
2021-09-10 19:03 ` [PATCH 3/4] dt-bindings: add vendor prefix for Wireless Tag Romain Perier
2021-09-11 2:59 ` Daniel Palmer
2021-09-11 12:20 ` Romain Perier [this message]
2021-09-10 19:03 ` [PATCH 4/4] MAINTAINERS: Add myself as MStar/Sigmastar Armv7 SoC maintainers Romain Perier
2021-09-11 2:56 ` Daniel Palmer
2021-09-14 13:54 ` Arnd Bergmann
2021-09-14 15:04 ` Daniel Palmer
2021-09-14 15:26 ` Arnd Bergmann
2021-09-14 17:09 ` Romain Perier
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='CABgxDo+9WnjE5pu=ijN01htLucFYko--w2fJ+ZVazBg_cSLZ1w@mail.gmail.com' \
--to=romain.perier@gmail.com \
--cc=arnd@arndb.de \
--cc=daniel@0x0f.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=soc@kernel.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).