From: "Heiko Stübner" <heiko@sntech.de>
To: Luis Garcia <git@luigi311.com>
Cc: devicetree@vger.kernel.org, linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
Olivier Benjamin <olivier.benjamin@bootlin.com>,
megi@xff.cz
Subject: Re: [PATCH 0/1] Fix imx258 variant on pinephone pro
Date: Wed, 21 Jan 2026 10:12:42 +0100 [thread overview]
Message-ID: <50650709.fMDQidcC6G@diego> (raw)
In-Reply-To: <46730110-5713-4e7a-a593-29ad69432e03@luigi311.com>
Hi,
Am Dienstag, 20. Januar 2026, 17:33:37 Mitteleuropäische Normalzeit schrieb Luis Garcia:
> Thank you very much for the speedy turn around. Ohh
> interesting, here i was thinking i did the right thing with
> the reply to with the V2. Ill keep that in mind for the
> future but considering how far and few my contributions
> upstream are i hope i dont forget by then lol.
no worries. For individual patches this is mostly easy to figure out
and also recent versions of b4 handled this thread fine.
I think it's more a problem, once the thread goes deeper or multiple
patches are involved.
Heiko
> On 1/20/26 02:39, Heiko Stuebner wrote:
> > On Sun, 18 Jan 2026 14:46:19 -0700, Luis Garcia wrote:
> >> imx258 had the driver updated a while back and it introduced
> >> two variants, the imx258 and imx258-pdaf. The pinephone pro
> >> is using the pdaf variant so this switches it to the correct
> >> variant and eliminates the pdaf pixels from the sensor output
> >> resulting in a much cleaner image.
> >>
> >> Luis Garcia (1):
> >> arm64: dts: rockchip: Fix imx258 variant on pinephone pro
> >>
> >> [...]
> > Applied, thanks!
> >
> > [1/1] arm64: dts: rockchip: Fix imx258 variant on pinephone pro
> > commit: 6742b998166485558ccb0e89b5d5fd93c1aae3ca
> >
> > In the future, please don't send v2 patches as replies to the
> > previous version and instead start a new thread.
> >
> > Next versions as replies, does sometimes confusing tooling.
> >
> >
> > Best regards,
>
prev parent reply other threads:[~2026-01-21 9:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-18 21:46 [PATCH 0/1] Fix imx258 variant on pinephone pro Luis Garcia
2026-01-18 21:46 ` [PATCH 1/1] arm64: dts: rockchip: " Luis Garcia
2026-01-18 22:19 ` [PATCH 0/1] " Ondřej Jirman
2026-01-19 1:06 ` [PATCH v2] arm64: dts: rockchip: " Luis Garcia
2026-01-20 9:39 ` [PATCH 0/1] " Heiko Stuebner
2026-01-20 16:33 ` Luis Garcia
2026-01-21 9:12 ` Heiko Stübner [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=50650709.fMDQidcC6G@diego \
--to=heiko@sntech.de \
--cc=devicetree@vger.kernel.org \
--cc=git@luigi311.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=megi@xff.cz \
--cc=olivier.benjamin@bootlin.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