Re: [PATCH 0/7] arm64: dts: qcom: IdeaCentre Mini 01Q8X10 Hamoa + Purwa

[Bjorn Andersson]

On Tue, Sep 08, 2026 at 11:02:40AM +0000, Mostafa Saleh wrote:
> On Tue, Sep 08, 2026 at 11:57:33AM +0200, Konrad Dybcio wrote:
> > On 9/8/26 11:11 AM, Mostafa Saleh wrote:
> > > On Tue, Sep 08, 2026 at 11:05:34AM +0200, Krzysztof Kozlowski wrote:
> > >> On 08/09/2026 11:03, Mostafa Saleh wrote:
> > >>> Hi Jens,
> > >>>
> > >>> On Sat, Sep 05, 2026 at 11:28:55AM +0200, Jens Glathe via B4 Relay wrote:
> > >>>> The IdeaCentre Mini 01Q8X10 (board 91B6) ships with two SoCs: Hamoa
> > >>>> (X1E80100), already upstream, and Purwa (X1P42100 / X1-26-100). Same
> > >>>> chassis, different silicon. Stubble and the DTB loader need distinct
> > >>>> compatibles.
> > 
> > [...]
> > 
> > >>>> base-commit: af5f12805e5cefa4fe68d6127c7e1fb78cd5535c
> > >>>
> > >>> This series does not apply to ToT nor I can find this base-commit
> > >>> in it.
> > >>
> > >> It's a public/standard commit, next.
> > >>
> > >> What is ToT in upstream development?
> > > 
> > > I am using Linus's Tree:
> > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/log/
> > 
> > This tree contains the latest release/rc tags, linux-next is an
> > aggreagation of each submaintainers' branches, effectively "what is
> > the next release going to look like" so essentially that's where the
> > development happens
> 
> AFAIU, linux-next is useful to get a view of the next release.

That's exactly the reason why you should develop on linux-next, it gives
you the view of how your patches fits together with the other changes
staged for that next release - before we try to merge them.

> However,
> it shouldn't be used for developement. It should be either Linus's tree
> or the maintainer's tree (as mentioned in process/submitting-patches)
> 

Please develop and test on linux-next.

Regards,
Bjorn

> Thanks,
> Mostafa
> 
> > 
> > Konrad