From: Wolfram Sang <wsa@the-dreams.de>
To: Stefan Agner <stefan@agner.ch>
Cc: mark.rutland@arm.com, arnd@arndb.de, shawnguo@kernel.org,
mpe@ellerman.id.au, paulus@samba.org, benh@kernel.crashing.org,
scottwood@freescale.com, dinguyen@opensource.altera.com,
robh+dt@kernel.org, pawel.moll@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] Documentation: dt: i2c: use correct STMicroelectronics vendor prefix
Date: Tue, 28 Jun 2016 23:37:48 +0200 [thread overview]
Message-ID: <20160628213747.GC1598@katana> (raw)
In-Reply-To: <20160626093406.26785-1-stefan@agner.ch>
[-- Attachment #1: Type: text/plain, Size: 647 bytes --]
On Sun, Jun 26, 2016 at 02:34:04AM -0700, Stefan Agner wrote:
> The documentation currently uses the non-standard vendor prefix stm
> and st-micro for STMicroelectronics. The drivers do not specify the
> vendor prefixes since the I2C Core strips them away from the DT
Note that people are working on changing that behaviour. Shouldn't
affect this patch, though.
> provided compatible string. Therefor, changing documentation and
> existing device trees does not have any impact on device detection.
>
> Signed-off-by: Stefan Agner <stefan@agner.ch>
Acked-by: Wolfram Sang <wsa@the-dreams.de>
I am fine with Rob taking this.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-06-28 21:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-26 9:34 [PATCH 1/3] Documentation: dt: i2c: use correct STMicroelectronics vendor prefix Stefan Agner
2016-06-26 9:34 ` [PATCH 2/3] powerpc/dts: fix STMicroelectronics compatible strings Stefan Agner
2016-06-26 9:34 ` [PATCH 3/3] ARM: dts: " Stefan Agner
2016-06-28 20:56 ` [PATCH 1/3] Documentation: dt: i2c: use correct STMicroelectronics vendor prefix Rob Herring
2016-06-28 21:37 ` Wolfram Sang [this message]
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=20160628213747.GC1598@katana \
--to=wsa@the-dreams.de \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@opensource.altera.com \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=scottwood@freescale.com \
--cc=shawnguo@kernel.org \
--cc=stefan@agner.ch \
/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).