From: Rob Herring <robh@kernel.org>
To: Pawel Dembicki <paweldembicki@gmail.com>
Cc: Hao Fang <fanghao11@huawei.com>, Sam Ravnborg <sam@ravnborg.org>,
Linus Walleij <linus.walleij@linaro.org>,
Shawn Guo <shawnguo@kernel.org>,
devicetree@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
Corentin Labbe <clabbe@baylibre.com>,
linux-kernel@vger.kernel.org,
Oleksij Rempel <linux@rempel-privat.de>,
Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH v2 1/2] dt-bindings: vendor-prefixes: Add Ctera Networks
Date: Wed, 16 Feb 2022 17:42:53 -0600 [thread overview]
Message-ID: <Yg2L/eqJuZuYeub8@robh.at.kernel.org> (raw)
In-Reply-To: <20220215163926.894-2-paweldembicki@gmail.com>
On Tue, 15 Feb 2022 17:39:23 +0100, Pawel Dembicki wrote:
> CTERA Networks Intl. is a company based in Israel.
> They manufacture NASes, network devices and provide software
> products for cloud storage and IT security.
>
> Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
> ---
> v2: no changes
>
> 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:[~2022-02-16 23:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 16:39 [PATCH v2 2/2] ARM: dts: kirkwood: Add Ctera C-200 V1 board Pawel Dembicki
2022-02-15 16:39 ` [PATCH v2 1/2] dt-bindings: vendor-prefixes: Add Ctera Networks Pawel Dembicki
2022-02-16 23:42 ` Rob Herring [this message]
2022-02-15 18:25 ` [PATCH v2 2/2] ARM: dts: kirkwood: Add Ctera C-200 V1 board Andrew Lunn
2022-02-15 20:56 ` Paweł Dembicki
2022-02-15 21:14 ` Andrew Lunn
2022-02-15 21:14 ` Andrew Lunn
2022-02-28 16:24 ` Gregory CLEMENT
2022-02-28 23:43 ` Linus Walleij
2022-03-01 20:32 ` Paweł Dembicki
2022-03-01 22:04 ` Linus Walleij
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=Yg2L/eqJuZuYeub8@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=clabbe@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=fanghao11@huawei.com \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rempel-privat.de \
--cc=paweldembicki@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.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).