From: Rob Herring <robh@kernel.org>
To: "Uwe Kleine-König" <uwe@kleine-koenig.org>
Cc: devicetree@vger.kernel.org, Heiko Stuebner <heiko@sntech.de>,
Aditya Prayoga <aditya@kobol.io>,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
Johan Jonker <jbx6244@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 1/2] dt-bindings: vendor-prefixes: Add kobol prefix
Date: Fri, 16 Oct 2020 11:20:30 -0500 [thread overview]
Message-ID: <20201016162030.GA1520851@bogus> (raw)
In-Reply-To: <20201014200030.845759-2-uwe@kleine-koenig.org>
On Wed, 14 Oct 2020 22:00:29 +0200, Uwe Kleine-König wrote:
> The prefix is already used in arm/armada-388-helios4.dts.
>
> Signed-off-by: Uwe Kleine-König <uwe@kleine-koenig.org>
> ---
> Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
> 1 file changed, 2 insertions(+)
>
Please add Acked-by/Reviewed-by tags when posting new versions. However,
there's no need to repost patches *only* to add the tags. The upstream
maintainer will do that for acks received on the version they apply.
If a tag was not added on purpose, please state why and what changed.
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2020-10-16 16:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-14 20:00 [PATCH v4 0/2] arm64: Add basic support for Kobol's Helios64 Uwe Kleine-König
2020-10-14 20:00 ` [PATCH v4 1/2] dt-bindings: vendor-prefixes: Add kobol prefix Uwe Kleine-König
2020-10-16 16:20 ` Rob Herring [this message]
2020-10-17 21:31 ` Uwe Kleine-König
2020-10-14 20:00 ` [PATCH v4 2/2] arm64: dts: rockchip: Add basic support for Kobol's Helios64 Uwe Kleine-König
2020-11-02 14:55 ` [PATCH v4 0/2] arm64: " Heiko Stuebner
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=20201016162030.GA1520851@bogus \
--to=robh@kernel.org \
--cc=aditya@kobol.io \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=jbx6244@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=uwe@kleine-koenig.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).