From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 2/4] DT: Vendor prefixes: Add ricoh, ssi and synology
Date: Tue, 18 Feb 2014 10:29:25 +0100 [thread overview]
Message-ID: <20140218092925.GB17984@lunn.ch> (raw)
In-Reply-To: <5302A428.3060708@killerwolves.net>
On Tue, Feb 18, 2014 at 10:07:04AM +1000, Ben Peddell wrote:
> On 18/02/2014 8:34 AM, Josh Cartwright wrote:
> > On Tue, Feb 18, 2014 at 07:45:35AM +1000, klightspeed at killerwolves.net wrote:
> >> From: Andrew Lunn <andrew@lunn.ch>
> >>
> >> The following patches make use of vendor names ricoh, ssi and
> >> synology. Add them to the vendor prefix list.
> >>
> >> Signed-off-by: Andrew Lunn <andrew@lunn.ch>
> >> Acked-by: Jason Cooper <jason@lakedaemon.net>
> >> ---
> >> v2:
> >> Use stock ticker for Ricoh as vendor name
> >> s/Richoh/Ricoh/
> >> ---
> >> Documentation/devicetree/bindings/vendor-prefixes.txt | 3 +++
> >> 1 file changed, 3 insertions(+)
> >>
> >> diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt b/Documentation/devicetree/bindings/vendor-prefixes.txt
> >> index 40ce2df..8427681 100644
> >> --- a/Documentation/devicetree/bindings/vendor-prefixes.txt
> >> +++ b/Documentation/devicetree/bindings/vendor-prefixes.txt
> >> @@ -72,6 +72,7 @@ ralink Mediatek/Ralink Technology Corp.
> >> ramtron Ramtron International
> >> realtek Realtek Semiconductor Corp.
> >> renesas Renesas Electronics Corporation
> >> +ricoy Ricoh Co. Ltd.
> >> rockchip Fuzhou Rockchip Electronics Co., Ltd
> >> samsung Samsung Semiconductor
> >> sbs Smart Battery System
> >> @@ -79,11 +80,13 @@ schindler Schindler
> >> sil Silicon Image
> >> silabs Silicon Laboratories
> >> simtek
> >> +sii Seiko Instruments, Inc.
> >> sirf SiRF Technology, Inc.
> >> snps Synopsys, Inc.
> >> st STMicroelectronics
> >> ste ST-Ericsson
> >> stericsson ST-Ericsson
> >> +synology Synology, Inc.
> >
> > Oh, great! Looks like this one is added (see my comment on patch 1).
> > I'm wondering if 'qnap' should be added as well.
>
> Do we want to use "qnap" or their ticker "qnapsz"?
>
Hi Ben
Ticker.
It might also make sense to re-arrange the order of these patches, so
that this one comes first and then the power off patch. However it is
not too important, because the patches are probably going to get split
up and go thought different maintainers.
Andrew
next prev parent reply other threads:[~2014-02-18 9:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-17 21:45 [PATCH v4 0/4] DT support for kirkwood based Synology NAS boxes klightspeed at killerwolves.net
2014-02-17 21:45 ` [PATCH v4 1/4] Power: Reset: Generalize qnap-poweroff to with on Synology devices klightspeed at killerwolves.net
2014-02-17 22:31 ` Josh Cartwright
2014-02-17 21:45 ` [PATCH v4 2/4] DT: Vendor prefixes: Add ricoh, ssi and synology klightspeed at killerwolves.net
2014-02-17 22:34 ` Josh Cartwright
2014-02-18 0:07 ` Ben Peddell
2014-02-18 9:29 ` Andrew Lunn [this message]
2014-02-17 22:40 ` Sebastian Reichel
2014-02-17 21:45 ` [PATCH v4 3/4] DT: i2c: Trivial: Add sii, s35390a, fix ricoh vendor prefix klightspeed at killerwolves.net
2014-02-17 21:45 ` [PATCH v4 4/4] ARM: Kirkwood: Add support for many Synology NAS devices klightspeed at killerwolves.net
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=20140218092925.GB17984@lunn.ch \
--to=andrew@lunn.ch \
--cc=linux-arm-kernel@lists.infradead.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).