From: Shawn Guo <shawnguo@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Linux ARM <linux-arm-kernel@lists.infradead.org>,
arm-soc <arm@kernel.org>, Fabio Estevam <festevam@gmail.com>,
linux-imx@nxp.com, Sascha Hauer <kernel@pengutronix.de>
Subject: Re: [GIT PULL 3/7] i.MX DT bindings update for 5.1
Date: Mon, 18 Feb 2019 09:16:26 +0800 [thread overview]
Message-ID: <20190218011624.GA6262@dragon> (raw)
In-Reply-To: <CAK8P3a1jj21UDq92L-gW0DeXZwyz55Ui8jdTpbi-K7Jy4mpO4w@mail.gmail.com>
On Fri, Feb 15, 2019 at 04:08:41PM +0100, Arnd Bergmann wrote:
> On Tue, Feb 12, 2019 at 12:21 PM Shawn Guo <shawnguo@kernel.org> wrote:
> >
> > Hi Arnd, Olof,
> >
> > In the past, I was simply using imx/dt branch to collect i.MX platform
> > related DT bindings changes, together with arm32 dts ones. Now with the
> > move to json-schema, we are using a single fsl.yaml file to accommodate
> > both arm32 and arm64 platform bindings, while we have separate branches
> > for dts changes - imx/dt and imx/dt64. To avoid conflicts, I chose to
> > create a new branch imx/bindings for i.MX platform bindings change for
> > this cycle. That's why we get this pull request, which you will pull
> > into arm-soc next/dt branch, I guess.
> >
> > For future cycles, I would like to hear your thoughts on if we can use
> > a single branch for both arm32 and arm64 dts changes, so that the
> > bindings changes can go in there too. Thanks.
>
> I'd say you could combine them if you have only a couple of changesets
> in total, but given the current size of the branches, I prefer having three
> or even more separate branches for the DT changes.
Got it. Thanks for the comment, Arnd.
Shawn
_______________________________________________
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-18 1:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 11:21 [GIT PULL 1/7] i.MX drivers update for 5.1 Shawn Guo
2019-02-12 11:21 ` [GIT PULL 2/7] i.MX SoC changes " Shawn Guo
2019-02-15 16:40 ` Arnd Bergmann
2019-02-12 11:21 ` [GIT PULL 3/7] i.MX DT bindings update " Shawn Guo
2019-02-15 15:08 ` Arnd Bergmann
2019-02-18 1:16 ` Shawn Guo [this message]
2019-02-12 11:21 ` [GIT PULL 4/7] i.MX device tree changes " Shawn Guo
2019-02-15 15:10 ` Arnd Bergmann
2019-02-12 11:21 ` [GIT PULL 5/7] i.MX arm64 " Shawn Guo
2019-02-15 15:11 ` Arnd Bergmann
2019-02-12 11:21 ` [GIT PULL 6/7] i.MX defconfig updates " Shawn Guo
2019-02-15 15:47 ` Arnd Bergmann
2019-02-12 11:21 ` [GIT PULL 7/7] i.MX MAINTAINERS update " Shawn Guo
2019-02-15 16:38 ` Arnd Bergmann
2019-02-15 17:03 ` Fabio Estevam
2019-02-15 16:18 ` [GIT PULL 1/7] i.MX drivers " 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=20190218011624.GA6262@dragon \
--to=shawnguo@kernel.org \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.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.