From: "Heiko Stübner" <heiko@sntech.de>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "open list:ARM/Rockchip SoC support"
<linux-rockchip@lists.infradead.org>, arm-soc <arm@kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL 2/2] Rockchip arm64 devicetree fixes for 5.0
Date: Fri, 15 Feb 2019 20:29:37 +0100 [thread overview]
Message-ID: <1949580.EMc7zAnHbR@diego> (raw)
In-Reply-To: <CAK8P3a3+6RuTEo=C0jkdiBswHrrKCSoxvYi3r60j45Sn6rhL3g@mail.gmail.com>
Am Freitag, 15. Februar 2019, 20:19:50 CET schrieb Arnd Bergmann:
> On Fri, Feb 15, 2019 at 7:38 PM Heiko Stübner <heiko@sntech.de> wrote:
> > Am Freitag, 15. Februar 2019, 13:42:48 CET schrieb Arnd Bergmann:
> > > On Fri, Feb 1, 2019 at 12:14 PM Heiko Stuebner <heiko@sntech.de> wrote:
> > > > ----------------------------------------------------------------
> > > > Fix for new dtc graph warnings and a regulator fix for rock64.
> > > >
> > > > ----------------------------------------------------------------
> > > >
> > > > Dmitry Voytik (1):
> > > > arm64: dts: rockchip: enable usb-host regulators at boot on
> > > > rk3328-rock64
> > >
> > > Pulled into arm/fixes, thanks!
> > >
> > > Note: since we always have only a single fixes branch, sending the
> > > 32-bit and 64-bit fixes together would be slightly easier.
> >
> > No problem, I'll keep 32+64bit fixes together in the future.
> > I guess regular changes for the merge-window should continue
> > being separated, right?
>
> Yes, unless they are logically connected. You can also have
> more than two DT pull requests if that makes a better split.
> Some SoCs have separate dt-bindings pull requests (shared
> with drivers), or split out stuff by SoC subfamily if it gets too
> big (probably not necessary for rockchips, which seem more
> uniform).
yeah, I think the split I had so far (dts32+dts64+drivers if necessary)
worked quite well so far, so I'll keep it :-)
_______________________________________________
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:[~2019-02-15 19:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-01 11:13 [GIT PULL 1/2] Rockchip arm32 devicetree fixes for 5.0 Heiko Stuebner
2019-02-01 11:14 ` [GIT PULL 2/2] Rockchip arm64 " Heiko Stuebner
2019-02-15 12:42 ` Arnd Bergmann
2019-02-15 18:37 ` Heiko Stübner
2019-02-15 19:19 ` Arnd Bergmann
2019-02-15 19:29 ` Heiko Stübner [this message]
2019-02-15 12:41 ` [GIT PULL 1/2] Rockchip arm32 " Arnd Bergmann
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=1949580.EMc7zAnHbR@diego \
--to=heiko@sntech.de \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.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).