[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20220805160034.GA29654@willie-the-truck>
Date: Fri, 5 Aug 2022 17:00:35 +0100
From: Will Deacon <will@...nel.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: catalin.marinas@....com, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, kernel-team@...roid.com,
maz@...nel.org
Subject: Re: [GIT PULL] arm64 updates for 5.20
On Tue, Aug 02, 2022 at 07:55:38AM -0700, Linus Torvalds wrote:
> On Tue, Aug 2, 2022 at 2:00 AM Will Deacon <will@...nel.org> wrote:
> >
> > Seriously though, if you could share any details about exactly how you're
> > running this (e.g. in a VM or native, .config, any extra patches on top)
> > then we could probably mimic it in CI to avoid any last minute surprises
> > with the pull requests.
>
> So my setup is basically an 2022 M2 Apple Macbook Air, with a Fedora
> spin of Asahi.
>
> I run it natively, but because not all of the Asahi kernel patches are
> in, currently I end up with two trees (exactly like my main desktop,
> actually): one that is my plain kernel that I run allmodconfig builds
> on, and a separate tree for "local boot testing".
>
> That "local boot testing" tree is basically the same tree except I
> merge in the Asahi kernel to get the drivers (that aren't upstream yet
> (it's 150+ patches for iommu, HID, GPIO, wireless, power, and dts
> files).
>
> The asahi side doesn't contain any actual architecture changes
> (outside of the dts files).
Thanks for the details, that sounds like it should be a reasonably
straightforward setup to repro locally at least.
Now to expense one of these fancy toys...
Will
Powered by blists - more mailing lists