From: Rob Herring <robh@kernel.org>
To: Claudiu Beznea <claudiu.beznea@microchip.com>
Cc: olof@lixom.net, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, arnd@arndb.de,
devicetree@vger.kernel.org, nicolas.ferre@microchip.com,
soc@kernel.org, ludovic.desroches@microchip.com,
robh+dt@kernel.org, alexandre.belloni@bootlin.com
Subject: Re: [PATCH 2/7] dt-bindings: add vendor prefix for exegin
Date: Fri, 13 Aug 2021 13:55:18 -0500 [thread overview]
Message-ID: <YRbAFrGzKv9s0mKe@robh.at.kernel.org> (raw)
In-Reply-To: <20210805155357.594414-3-claudiu.beznea@microchip.com>
On Thu, 05 Aug 2021 18:53:52 +0300, Claudiu Beznea wrote:
> Add vendor prefix for Exegin Technologies Limited.
>
> Signed-off-by: Claudiu Beznea <claudiu.beznea@microchip.com>
> ---
> Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
> 1 file changed, 2 insertions(+)
>
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2021-08-13 18:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-05 15:53 [PATCH 0/7] ARM: dts: at91: add Exegin Q5xR5 and CalAmp LMU5000 Claudiu Beznea
2021-08-05 15:53 ` [PATCH 1/7] ARM: dts: at91: at91sam9260: add pinctrl label Claudiu Beznea
2021-08-05 15:53 ` [PATCH 2/7] dt-bindings: add vendor prefix for exegin Claudiu Beznea
2021-08-13 18:55 ` Rob Herring [this message]
2021-08-05 15:53 ` [PATCH 3/7] dt-bindings: ARM: at91: document exegin q5xr5 board Claudiu Beznea
2021-08-13 18:55 ` Rob Herring
2021-08-13 18:58 ` Rob Herring
2021-08-05 15:53 ` [PATCH 4/7] ARM: dts: at91: add Exegin Q5xR5 board Claudiu Beznea
2021-08-05 15:53 ` [PATCH 5/7] dt-bindings: add vendor prefix for calamp Claudiu Beznea
2021-08-13 18:56 ` Rob Herring
2021-08-05 15:53 ` [PATCH 6/7] dt-bindings: ARM: at91: document CalAmp LMU5000 board Claudiu Beznea
2021-08-13 18:57 ` Rob Herring
2021-08-05 15:53 ` [PATCH 7/7] ARM: dts: at91: add " Claudiu Beznea
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=YRbAFrGzKv9s0mKe@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=arnd@arndb.de \
--cc=claudiu.beznea@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=nicolas.ferre@microchip.com \
--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).