From: Wolfram Sang <wsa@the-dreams.de>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Mark Rutland <mark.rutland@arm.com>,
Rob Herring <robh@kernel.org>,
devicetree <devicetree@vger.kernel.org>,
Russell King <linux@armlinux.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>,
linux-i2c <linux-i2c@vger.kernel.org>,
Peter Rosin <peda@axentia.se>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/4] dt-bindings: at24: sort manufacturers alphabetically
Date: Wed, 21 Feb 2018 10:11:30 +0100 [thread overview]
Message-ID: <20180221091130.4sdfnalrng4sd77i@ninjato> (raw)
In-Reply-To: <CAMRc=Mcqj36KP7dG71dzSn_7cxw-Tru5kNtXdr5-SiH=jbCfMA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 814 bytes --]
On Mon, Jan 29, 2018 at 05:56:52PM +0100, Bartosz Golaszewski wrote:
> 2018-01-29 17:17 GMT+01:00 Rob Herring <robh@kernel.org>:
> > On Tue, Jan 16, 2018 at 05:06:15PM +0100, Peter Rosin wrote:
> >> Makes them easier to find.
> >>
> >> Signed-off-by: Peter Rosin <peda@axentia.se>
> >> ---
> >> Documentation/devicetree/bindings/eeprom/at24.txt | 2 +-
> >> 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > This one should go into 4.16. I can apply after rc1 or apply to tree
> > with at24.txt changes queued.
> >
> > Acked-by: Rob Herring <robh@kernel.org>
> >
> > Rob
>
> Wolfram,
>
> can you take this via the i2c tree for 4.16?
I missed this mail because I leave at24 patches to you now.
Please send pull requests for patches I shall take. Least room for
confusion (I hope).
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2018-02-21 9:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 16:06 [PATCH 0/4] use correct compatibles for the nxp,se97b chips Peter Rosin
2018-01-16 16:06 ` [PATCH 1/4] dt-bindings: at24: sort manufacturers alphabetically Peter Rosin
2018-01-16 17:26 ` Bartosz Golaszewski
[not found] ` <20180116160618.27859-2-peda-koto5C5qi+TLoDKTGw+V6w@public.gmane.org>
2018-01-29 16:17 ` Rob Herring
2018-01-29 16:56 ` Bartosz Golaszewski
2018-02-21 9:11 ` Wolfram Sang [this message]
2018-02-21 9:23 ` Bartosz Golaszewski
2018-02-21 9:40 ` Wolfram Sang
2018-02-23 7:52 ` Bartosz Golaszewski
2018-02-23 10:32 ` Wolfram Sang
2018-02-23 11:40 ` Bartosz Golaszewski
2018-02-28 9:28 ` Bartosz Golaszewski
2018-01-16 16:06 ` [PATCH 2/4] dt-bindings: at24: add compatible for nxp,se97b Peter Rosin
2018-01-16 17:26 ` Bartosz Golaszewski
2018-01-29 16:18 ` Rob Herring
2018-03-02 10:17 ` Bartosz Golaszewski
2018-01-16 16:06 ` [PATCH 3/4] ARM: dts: at91: nattis: use the correct compatible for the eeprom Peter Rosin
2018-01-30 22:15 ` Alexandre Belloni
2018-01-16 16:06 ` [PATCH 4/4] ARM: dts: at91: tse850: " Peter Rosin
2018-01-30 22:15 ` Alexandre Belloni
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=20180221091130.4sdfnalrng4sd77i@ninjato \
--to=wsa@the-dreams.de \
--cc=alexandre.belloni@free-electrons.com \
--cc=brgl@bgdev.pl \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=peda@axentia.se \
--cc=robh@kernel.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).