From: Rob Herring <robh+dt@kernel.org>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Thierry Reding <thierry.reding@gmail.com>,
Peter Rosin <peda@axentia.se>,
Linux I2C <linux-i2c@vger.kernel.org>,
devicetree@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] dt-bindings: i2c: Use correct vendor prefix for Atmel
Date: Mon, 3 Dec 2018 14:50:15 -0600 [thread overview]
Message-ID: <CAL_JsqJZJVMvd0aQJ8eDXBqiZ=quLrNGr3hhqePm8fCushHxxQ@mail.gmail.com> (raw)
In-Reply-To: <20181127125050.GO1107@kunai>
On Tue, Nov 27, 2018 at 6:50 AM Wolfram Sang <wsa@the-dreams.de> wrote:
>
> On Fri, Nov 23, 2018 at 01:51:38PM +0100, Thierry Reding wrote:
> > From: Thierry Reding <treding@nvidia.com>
> >
> > The "at," prefix was never correct for Atmel, so fix the few occurrences
> > that got it wrong. Use "atmel," instead.
> >
> > While at it, remove the at,24c08 compatible string from the list of
> > trivial devices because it is already documented in eeprom/at24.txt.
> >
> > Signed-off-by: Thierry Reding <treding@nvidia.com>
>
> Peter, I'd assume you are okay with me applying the patch directly?
Didn't we agree that I take trivial devices changes? Normally, it
doesn't really matter, but I'll have to delay landing the json-schema
conversion because this will conflict.
Rob
next prev parent reply other threads:[~2018-12-03 20:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-23 12:10 [PATCH] dt-bindings: i2c: Use correct vendor prefix for Atmel Thierry Reding
2018-11-23 12:40 ` Peter Rosin
2018-11-23 12:47 ` Thierry Reding
2018-11-23 12:51 ` [PATCH v2] " Thierry Reding
2018-11-27 12:50 ` Wolfram Sang
2018-11-27 15:48 ` Peter Rosin
2018-12-03 20:50 ` Rob Herring [this message]
2018-12-03 21:00 ` Wolfram Sang
2018-12-07 13:11 ` Wolfram Sang
2018-11-30 23:19 ` Wolfram Sang
2018-12-11 19:49 ` Wolfram Sang
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='CAL_JsqJZJVMvd0aQJ8eDXBqiZ=quLrNGr3hhqePm8fCushHxxQ@mail.gmail.com' \
--to=robh+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
--cc=thierry.reding@gmail.com \
--cc=wsa@the-dreams.de \
/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).