From: Maxime Ripard <maxime.ripard@bootlin.com>
To: Olof Johansson <olof@lixom.net>
Cc: Chen-Yu Tsai <wens@csie.org>,
ARM-SoC Maintainers <arm@kernel.org>,
Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL] Allwinner H3/H5 Device Tree Changes for 5.3
Date: Tue, 25 Jun 2019 14:53:26 +0200 [thread overview]
Message-ID: <20190625125326.y65zmy4iewfq74k2@flea> (raw)
In-Reply-To: <CAOesGMjKpQz3hnn+f_sahUAr9OVF59wDxvPKSU374FJvsWmMyA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1637 bytes --]
On Tue, Jun 25, 2019 at 02:37:13PM +0200, Olof Johansson wrote:
> On Tue, Jun 25, 2019 at 2:32 PM Maxime Ripard <maxime.ripard@bootlin.com> wrote:
> > On Tue, Jun 25, 2019 at 04:43:01AM -0700, Olof Johansson wrote:
> > > On Fri, Jun 21, 2019 at 10:13:14AM +0200, Maxime Ripard wrote:
> > > > Hi,
> > > >
> > > > Please pull the following changes for the next release.
> > > >
> > > > Thanks!
> > > > Maxime
> > > >
> > > > The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9:
> > > >
> > > > Linux 5.2-rc1 (2019-05-19 15:47:09 -0700)
> > > >
> > > > are available in the Git repository at:
> > > >
> > > > https://git.kernel.org/pub/scm/linux/kernel/git/sunxi/linux.git refs/tags/sunxi-h3-h5-for-5.3-201906210812
> > > >
> > > > for you to fetch changes up to 9fbbbb7b8d637f7ca1d5c4e23452bf450c7cb05f:
> > > >
> > > > ARM: dts: sunxi: h3/h5: Fix GPIO regulator state array (2019-05-29 09:27:56 +0200)
> > > >
> > > > ----------------------------------------------------------------
> > > > This time we only have a single patch for our command branch between
> > > > arm and arm64, a fix for the array syntax raised by our DT schemas.
> > >
> > > Merged, thanks!
> > >
> > > I don't think we'll start separating 32/64-bit DT updates again, so if you want
> > > to you can combine them now.
> >
> > Do you have a preference on which tree we should apply it to then?
>
> Oh, I meant you can bundle 32+64+h3-h5 in one branch at your end, so
> fold all 3 down to 1.
Oh, ok. That's going to be much more convenient :)
Maxime
--
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 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
prev parent reply other threads:[~2019-06-25 12:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 8:13 [GIT PULL] Allwinner H3/H5 Device Tree Changes for 5.3 Maxime Ripard
2019-06-25 11:43 ` Olof Johansson
2019-06-25 12:32 ` Maxime Ripard
2019-06-25 12:37 ` Olof Johansson
2019-06-25 12:53 ` Maxime Ripard [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=20190625125326.y65zmy4iewfq74k2@flea \
--to=maxime.ripard@bootlin.com \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=olof@lixom.net \
--cc=wens@csie.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