Message ID | 20220729102205.GA24050@willie-the-truck |
---|---|
State | New |
Headers | show |
Series | [GIT,PULL] arm64 updates for 5.20 | expand |
The pull request you sent on Fri, 29 Jul 2022 11:22:06 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git tags/arm64-upstream
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/0cec3f24a7cedc726f8790d693aaff2c535dc4ce
Thank you!
On Fri, Jul 29, 2022 at 3:22 AM Will Deacon <will@kernel.org> wrote: > > git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git tags/arm64-upstream .. and I can happily report that this works fine on my M2 Air. Which I'm sure is not any surprise, but it's still nice to be able to actually test and run these things. Linus
On Mon, Aug 01, 2022 at 12:24:15PM -0700, Linus Torvalds wrote: > On Fri, Jul 29, 2022 at 3:22 AM Will Deacon <will@kernel.org> wrote: > > > > git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git tags/arm64-upstream > > .. and I can happily report that this works fine on my M2 Air. > > Which I'm sure is not any surprise, but it's still nice to be able to > actually test and run these things. /me breathes out 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. Cheers, Will
On Tue, Aug 2, 2022 at 2:00 AM Will Deacon <will@kernel.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). Linus
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@kernel.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