From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Eric Andersson <eric.andersson@unixphere.com>,
linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org,
alan@lxorguk.ukuu.org.uk, zhengguang.guo@bosch-sensortec.com,
peter.moeller@cn.bosch.com, stefan.nilsson@unixphere.com,
devicetree-discuss@lists.ozlabs.org
Subject: Re: [PATCHv3 3/3] misc: add support for bmp18x chips to the bmp085 driver
Date: Wed, 4 Apr 2012 21:11:17 +0100 [thread overview]
Message-ID: <20120404201116.GC10787@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <201204042000.34160.arnd@arndb.de>
[-- Attachment #1: Type: text/plain, Size: 681 bytes --]
On Wed, Apr 04, 2012 at 08:00:33PM +0000, Arnd Bergmann wrote:
> On Wednesday 04 April 2012, Mark Brown wrote:
> > > +static const struct of_device_id bmp085_of_match[] = {
> > > + { .compatible = "bosch-sensortec,bmp085", },
> > Traditionally the stock ticker symbol would be used.
> I though about commenting on that as well, but since Bosch is a foundation
> and not publically traded, that would be hard to accomplish. Is there
> an official fallback for companies that don't have a stock ticker symbol?
Guess we should ask the DT people... I mostly just noticed that the
name appeared somewhat verbose - perhaps just plain "bosch" if there's
not a better abbrevation?
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next parent reply other threads:[~2012-04-04 20:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1333568759-13536-1-git-send-email-eric.andersson@unixphere.com>
[not found] ` <1333568759-13536-4-git-send-email-eric.andersson@unixphere.com>
[not found] ` <20120404195532.GB10787@opensource.wolfsonmicro.com>
[not found] ` <201204042000.34160.arnd@arndb.de>
2012-04-04 20:11 ` Mark Brown [this message]
2012-04-05 6:53 ` [PATCHv3 3/3] misc: add support for bmp18x chips to the bmp085 driver Eric Andersson
2012-04-07 1:37 ` Grant Likely
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=20120404201116.GC10787@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arnd@arndb.de \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=eric.andersson@unixphere.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.moeller@cn.bosch.com \
--cc=stefan.nilsson@unixphere.com \
--cc=zhengguang.guo@bosch-sensortec.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;
as well as URLs for NNTP newsgroup(s).