From: Rob Herring <robh@kernel.org>
To: Bert Vermeulen <bert@biot.com>
Cc: Birger Koblitz <mail@birger-koblitz.de>,
Sander Vanheule <sander@svanheule.net>,
John Crispin <john@phrozen.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
linux-mips@vger.kernel.org, Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH v4 4/5] dt-bindings: Add Cisco prefix to vendor list
Date: Wed, 20 Jan 2021 09:50:28 -0600 [thread overview]
Message-ID: <20210120155028.GB213895@robh.at.kernel.org> (raw)
In-Reply-To: <20210119092109.185282-5-bert@biot.com>
On Tue, 19 Jan 2021 10:21:08 +0100, Bert Vermeulen wrote:
> Signed-off-by: Bert Vermeulen <bert@biot.com>
> ---
> 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.
next prev parent reply other threads:[~2021-01-20 16:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-19 9:21 [PATCH v4 0/5] Add support for Realtek RTL838x/RTL839x switch SoCs Bert Vermeulen
2021-01-19 9:21 ` [PATCH v4 1/5] dt-bindings: mips: Add support for RTL83xx SoC series Bert Vermeulen
2021-01-19 9:21 ` [PATCH v4 2/5] Add support for Realtek RTL838x/RTL839x switch SoCs Bert Vermeulen
2021-01-19 9:21 ` [PATCH v4 3/5] MIPS: Add Realtek RTL838x/RTL839x support as generic MIPS system Bert Vermeulen
2021-01-19 9:21 ` [PATCH v4 4/5] dt-bindings: Add Cisco prefix to vendor list Bert Vermeulen
2021-01-20 15:50 ` Rob Herring [this message]
2021-01-19 9:21 ` [PATCH v4 5/5] mips: dts: Add support for Cisco SG220-26 switch Bert Vermeulen
2021-02-04 20:59 ` Thomas Bogendoerfer
2021-02-04 20:57 ` [PATCH v4 0/5] Add support for Realtek RTL838x/RTL839x switch SoCs Thomas Bogendoerfer
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=20210120155028.GB213895@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=bert@biot.com \
--cc=devicetree@vger.kernel.org \
--cc=john@phrozen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=mail@birger-koblitz.de \
--cc=robh+dt@kernel.org \
--cc=sander@svanheule.net \
--cc=tsbogend@alpha.franken.de \
/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).