From: Wolfram Sang <wsa@the-dreams.de>
To: Rob Herring <robh+dt@kernel.org>
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: Fri, 7 Dec 2018 14:11:08 +0100 [thread overview]
Message-ID: <20181207131108.GA2462@kunai> (raw)
In-Reply-To: <20181203210035.GA4611@kunai>
[-- Attachment #1: Type: text/plain, Size: 686 bytes --]
On Mon, Dec 03, 2018 at 10:00:35PM +0100, Wolfram Sang wrote:
>
> > 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.
>
> Oh, sorry, I missed that! I haven't send my pull request to Linus, so I
> can easily drop this patch again and apply a version not touching
> trivial-devices instead.
For the record, I really dropped this patch from my for-current queue
and will apply it to my for-next queue without the 'trivial-devices'
change once we agreed how to handle Bartosz' incremental patch on top of
it. I hope this fits your needs.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-12-07 13:11 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
2018-12-03 21:00 ` Wolfram Sang
2018-12-07 13:11 ` Wolfram Sang [this message]
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=20181207131108.GA2462@kunai \
--to=wsa@the-dreams.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.