From: Rob Herring <robh@kernel.org>
To: Mathew McBride <matt@traverse.com.au>
Cc: Shawn Guo <shawnguo@kernel.org>, Li Yang <leoyang.li@nxp.com>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, Ioana Ciornei <ioana.ciornei@nxp.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 3/5] dt-bindings: vendor-prefixes: add Traverse Technologies
Date: Thu, 29 Jul 2021 16:41:28 -0600 [thread overview]
Message-ID: <YQMumLDkN1JX0YwW@robh.at.kernel.org> (raw)
In-Reply-To: <20210726071216.22711-4-matt@traverse.com.au>
On Mon, 26 Jul 2021 07:12:14 +0000, Mathew McBride wrote:
> Traverse Technologies is a designer and manufacturer
> of networking appliances.
>
> Signed-off-by: Mathew McBride <matt@traverse.com.au>
> ---
> Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
> 1 file changed, 2 insertions(+)
>
Acked-by: Rob Herring <robh@kernel.org>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-07-29 22:43 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-22 4:24 [PATCH 0/5] Add Traverse Technologies Ten64 board DTS Mathew McBride
2021-07-22 4:24 ` [PATCH 1/5] arm64: dts: ls1088a: add internal PCS for DPMAC1 node Mathew McBride
2021-07-22 7:48 ` Ioana Ciornei
2021-07-22 4:24 ` [PATCH 2/5] arm64: dts: ls1088a: add missing PMU node Mathew McBride
2021-07-23 8:36 ` Shawn Guo
2021-07-22 4:24 ` [PATCH 3/5] dt-bindings: vendor-prefixes: add Traverse Technologies Mathew McBride
2021-07-22 4:24 ` [PATCH 4/5] dt-bindings: arm: fsl: Add Traverse Ten64 (LS1088A) board Mathew McBride
2021-07-22 4:24 ` [PATCH 5/5] arm64: dts: add device tree for Traverse Ten64 (LS1088A) Mathew McBride
2021-07-22 8:44 ` Ioana Ciornei
2021-07-23 9:46 ` Shawn Guo
2021-07-26 7:12 ` [PATCH v2 0/5] Add Traverse Technologies Ten64 board DTS Mathew McBride
2021-07-26 7:12 ` [PATCH v2 1/5] arm64: dts: ls1088a: add internal PCS for DPMAC1 node Mathew McBride
2021-07-26 7:12 ` [PATCH v2 2/5] arm64: dts: ls1088a: add missing PMU node Mathew McBride
2021-07-26 7:12 ` [PATCH v2 3/5] dt-bindings: vendor-prefixes: add Traverse Technologies Mathew McBride
2021-07-29 22:41 ` Rob Herring [this message]
2021-07-26 7:12 ` [PATCH v2 4/5] dt-bindings: arm: fsl: Add Traverse Ten64 (LS1088A) board Mathew McBride
2021-07-29 22:45 ` Rob Herring
2021-07-26 7:12 ` [PATCH v2 5/5] arm64: dts: add device tree for Traverse Ten64 (LS1088A) Mathew McBride
2021-07-29 22:45 ` Rob Herring
2021-08-10 5:38 ` [PATCH v3 0/5] Add Traverse Technologies Ten64 board DTS Mathew McBride
2021-08-10 5:38 ` [PATCH v3 1/5] arm64: dts: ls1088a: add internal PCS for DPMAC1 node Mathew McBride
2021-08-10 5:38 ` [PATCH v3 2/5] arm64: dts: ls1088a: add missing PMU node Mathew McBride
2021-08-10 5:38 ` [PATCH v3 3/5] dt-bindings: vendor-prefixes: add Traverse Technologies Mathew McBride
2021-08-10 5:38 ` [PATCH v3 4/5] dt-bindings: arm: fsl: Add Traverse Ten64 (LS1088A) board Mathew McBride
2021-08-10 5:38 ` [PATCH v3 5/5] arm64: dts: add device tree for Traverse Ten64 (LS1088A) Mathew McBride
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=YQMumLDkN1JX0YwW@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ioana.ciornei@nxp.com \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=matt@traverse.com.au \
--cc=robh+dt@kernel.org \
--cc=shawnguo@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).