From: "Andreas Färber" <afaerber@suse.de>
To: thesven73@gmail.com, svendev@arcx.com
Cc: lee.jones@linaro.org, robh+dt@kernel.org, mark.rutland@arm.com,
treding@nvidia.com, david@lechnology.com, noralf@tronnes.org,
johan@kernel.org, monstr@monstr.eu, michal.vokac@ysoft.com,
arnd@arndb.de, gregkh@linuxfoundation.org, john.garry@huawei.com,
geert+renesas@glider.be, robin.murphy@arm.com,
paul.gortmaker@windriver.com,
sebastien.bourdelin@savoirfairelinux.com, icenowy@aosc.io,
stuyoder@gmail.com, linus.walleij@linaro.org,
maxime.ripard@bootlin.com, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH anybus v2 2/5] dt-bindings: anybus-bridge: document devicetree binding.
Date: Thu, 1 Nov 2018 00:29:52 +0100 [thread overview]
Message-ID: <999e50d3-924d-b960-ffb2-b1ee04c08d09@suse.de> (raw)
In-Reply-To: <20181031194425.32132-3-TheSven73@googlemail.com>
Hi Sven,
Am 31.10.18 um 20:44 schrieb thesven73@gmail.com:
> From: Sven Van Asbroeck <svendev@arcx.com>
>
> This patch adds devicetree binding documentation for the
> Arcx anybus bridge.
>
> Signed-off-by: Sven Van Asbroeck <svendev@arcx.com>
> ---
> .../bindings/misc/arcx,anybus-bridge.txt | 34 +++++++++++++++++++
> .../devicetree/bindings/vendor-prefixes.txt | 1 +
> 2 files changed, 35 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/misc/arcx,anybus-bridge.txt
[...]
> diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt b/Documentation/devicetree/bindings/vendor-prefixes.txt
> index 2c3fc512e746..1bf07b20a8af 100644
> --- a/Documentation/devicetree/bindings/vendor-prefixes.txt
> +++ b/Documentation/devicetree/bindings/vendor-prefixes.txt
> @@ -35,6 +35,7 @@ aptina Aptina Imaging
> arasan Arasan Chip Systems
> archermind ArcherMind Technology (Nanjing) Co., Ltd.
> arctic Arctic Sand
> +arcx Arcx/Archronix Inc.
> aries Aries Embedded GmbH
> arm ARM Ltd.
> armadeus ARMadeus Systems SARL
Please move this to a separate patch, titled "dt-bindings: Add vendor
prefix for Arcx", with the commit message describing what the company does.
Also note that subject lines usually do not end with a full stop,
similar to book titles or news headlines.
And it is usually preferable to have such a long list of people in CC
rather than in To, to make it clear whom you expect to handle it and to
facilitate replies going to you without hand-editing every other To.
I notice that arcx.com spells it ARCX Inc., in upper-case without any
mention of Archronix in the name. So if that's a previous name you may
want to write it as "ARCX Inc. (formerly Archronix Inc.)"? Look for
other examples in that file.
Regards,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2018-10-31 23:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 19:44 [PATCH anybus v2 0/5] Support HMS Profinet Card over Anybus thesven73
2018-10-31 19:44 ` [PATCH anybus v2 1/5] misc: support the Arcx anybus bridge thesven73
2018-10-31 23:15 ` Linus Walleij
2018-11-01 17:17 ` Sven Van Asbroeck
2018-11-01 21:53 ` Linus Walleij
2018-11-02 14:16 ` Sven Van Asbroeck
2018-10-31 19:44 ` [PATCH anybus v2 2/5] dt-bindings: anybus-bridge: document devicetree binding thesven73
2018-10-31 23:29 ` Andreas Färber [this message]
2018-10-31 19:44 ` [PATCH anybus v2 3/5] bus: support HMS Anybus-S bus thesven73
2018-11-15 0:19 ` kbuild test robot
2018-10-31 19:44 ` [PATCH anybus v2 4/5] dt-bindings: anybuss-host: document devicetree binding thesven73
2018-10-31 19:44 ` [PATCH anybus v2 5/5] misc: support HMS Profinet IRT industrial controller thesven73
2018-11-01 16:03 ` kbuild test robot
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=999e50d3-924d-b960-ffb2-b1ee04c08d09@suse.de \
--to=afaerber@suse.de \
--cc=arnd@arndb.de \
--cc=david@lechnology.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=icenowy@aosc.io \
--cc=johan@kernel.org \
--cc=john.garry@huawei.com \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@bootlin.com \
--cc=michal.vokac@ysoft.com \
--cc=monstr@monstr.eu \
--cc=noralf@tronnes.org \
--cc=paul.gortmaker@windriver.com \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
--cc=sebastien.bourdelin@savoirfairelinux.com \
--cc=stuyoder@gmail.com \
--cc=svendev@arcx.com \
--cc=thesven73@gmail.com \
--cc=treding@nvidia.com \
/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
all inboxes | Powered by JetHome®