From: Rob Herring <robh@kernel.org>
To: "André Draszik" <andre.draszik@linaro.org>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Peter Griffin <peter.griffin@linaro.org>,
Tudor Ambarus <tudor.ambarus@linaro.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
Will McVicker <willmcvicker@google.com>,
kernel-team@android.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH 3/4] arm64: dts: exynos: gs101-oriole: move common Pixel6 & 6Pro parts into a .dtsi
Date: Wed, 18 Dec 2024 13:16:31 -0600 [thread overview]
Message-ID: <20241218191631.GA1837559-robh@kernel.org> (raw)
In-Reply-To: <6e22585f8d374f8e26a2a51153680041ad8b1bea.camel@linaro.org>
On Tue, Dec 17, 2024 at 08:34:50AM +0000, André Draszik wrote:
> On Tue, 2024-12-17 at 08:38 +0100, Krzysztof Kozlowski wrote:
> > On Mon, Dec 16, 2024 at 01:06:28PM +0000, André Draszik wrote:
> > > In order to support Pixel 6 (Oriole) and Pixel 6 Pro (Raven) properly,
> > > we have to be able to distinguish them properly as we add support for
> > > more features.
> > >
> > > For example, Raven has a larger display. There are other differences,
> > > like battery design capacity, etc.
> > >
> > > Move all the parts that are common for now into a gs101-raviole.dtsi,
> > > and just leave the display related things in gs101-oriole.dts.
> > >
> > > Raviole was chosen as the name because Google uses that when referring
> > > to the combination of Oriole & Raven, keeping the familiar terminology.
> > >
> > > Signed-off-by: André Draszik <andre.draszik@linaro.org>
> > >
> > > ---
> > > Note: MAINTAINERS doesn't need updating, it covers this whole directory
> > > ---
> > > arch/arm64/boot/dts/exynos/google/gs101-oriole.dts | 290 +-------------------
> > > .../boot/dts/exynos/google/gs101-raviole.dtsi | 297 +++++++++++++++++++++
> > > 2 files changed, 305 insertions(+), 282 deletions(-)
> > >
> >
> > This looks like move of the code, so -M/-B/-C format patch arguments
> > would create better diff.
>
> Ah, yes, forgot about those when I switched to using b4 instead of
> custom scripts...
If b4 does not do that by default, then it should set the option. One
less thing to get right for users. I sent a patch for that.
Rob
next prev parent reply other threads:[~2024-12-18 19:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-16 13:06 [PATCH 0/4] Google Pixel 6 (simple) framebuffer support André Draszik
2024-12-16 13:06 ` [PATCH 1/4] dt-bindings: arm: google: add gs101-raven André Draszik
2024-12-18 12:15 ` Peter Griffin
2024-12-18 19:17 ` Rob Herring (Arm)
2024-12-16 13:06 ` [PATCH 2/4] arm64: dts: exynos: gs101-oriole: configure simple-framebuffer André Draszik
2024-12-18 12:17 ` Peter Griffin
2024-12-16 13:06 ` [PATCH 3/4] arm64: dts: exynos: gs101-oriole: move common Pixel6 & 6Pro parts into a .dtsi André Draszik
2024-12-17 7:38 ` Krzysztof Kozlowski
2024-12-17 8:34 ` André Draszik
2024-12-18 19:16 ` Rob Herring [this message]
2024-12-18 12:14 ` Peter Griffin
2024-12-18 12:36 ` Krzysztof Kozlowski
2024-12-16 13:06 ` [PATCH 4/4] arm64: dts: exynos: gs101-raven: add new board file André Draszik
2024-12-17 7:39 ` Krzysztof Kozlowski
2024-12-17 8:35 ` André Draszik
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=20241218191631.GA1837559-robh@kernel.org \
--to=robh@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=andre.draszik@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel-team@android.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=peter.griffin@linaro.org \
--cc=tudor.ambarus@linaro.org \
--cc=willmcvicker@google.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 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).