From: Mark Rutland <mark.rutland@arm.com>
To: Kumar Gala <galak@codeaurora.org>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Felipe Balbi <balbi@ti.com>,
devicetree <devicetree@vger.kernel.org>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
Pawel Moll <Pawel.Moll@arm.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Rob Landley <rob@landley.net>
Subject: Re: [PATCH 1/2] of: add vendor prefix for Mentor Graphics
Date: Mon, 6 Jan 2014 18:30:00 +0000 [thread overview]
Message-ID: <20140106183000.GL24664@e106331-lin.cambridge.arm.com> (raw)
In-Reply-To: <D53158FF-7BCF-4BA8-A589-B6365B4DA058@codeaurora.org>
On Fri, Dec 20, 2013 at 05:26:02PM +0000, Kumar Gala wrote:
>
> On Dec 19, 2013, at 10:25 AM, Sebastian Andrzej Siewior <bigeasy@linutronix.de> wrote:
>
> > This prefix is currently used for the musb driver.
> >
> > Acked-by: Stephen Warren <swarren@nvidia.com>
> > Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> > ---
> > Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt b/Documentation/devicetree/bindings/vendor-prefixes.txt
> > index 8c75d85..cb5c438 100644
> > --- a/Documentation/devicetree/bindings/vendor-prefixes.txt
> > +++ b/Documentation/devicetree/bindings/vendor-prefixes.txt
> > @@ -43,6 +43,7 @@ linux Linux-specific binding
> > lsi LSI Corp. (LSI Logic)
> > marvell Marvell Technology Group Ltd.
> > maxim Maxim Integrated Products
> > +mentor Mentor Graphics
>
> file like we should use ‘ment’, but not sure if we are going away from ticker symbols or not.
In general we've been heading towards full names rather than stock
ticker symbols. It's far easier for a human to make an educated guess
without searching.
I'm certainly happy with mentor as a vendor prefix.
Mark.
>
> > microchip Microchip Technology Inc.
> > mosaixtech Mosaix Technologies, Inc.
> > national National Semiconductor
> > --
> > 1.8.5.1
> >
>
> - k
>
> --
> Employee of Qualcomm Innovation Center, Inc.
> Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
>
>
next prev parent reply other threads:[~2014-01-06 18:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 16:25 [PATCH 1/2] of: add vendor prefix for Mentor Graphics Sebastian Andrzej Siewior
2013-12-19 16:25 ` [PATCH 2/2] input: ti_am33x_tsc: make the documentation for the ti,wire-config parameter clear Sebastian Andrzej Siewior
2013-12-20 17:26 ` [PATCH 1/2] of: add vendor prefix for Mentor Graphics Kumar Gala
2014-01-06 18:30 ` Mark Rutland [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-08-20 16:40 Sebastian Andrzej Siewior
2013-08-20 19:03 ` Stephen Warren
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=20140106183000.GL24664@e106331-lin.cambridge.arm.com \
--to=mark.rutland@arm.com \
--cc=Pawel.Moll@arm.com \
--cc=balbi@ti.com \
--cc=bigeasy@linutronix.de \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=swarren@wwwdotorg.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).