From: Will Deacon <will@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: catalin.marinas@arm.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel-team@android.com,
maz@kernel.org
Subject: Re: [GIT PULL] arm64 updates for 5.20
Date: Fri, 5 Aug 2022 17:00:35 +0100 [thread overview]
Message-ID: <20220805160034.GA29654@willie-the-truck> (raw)
In-Reply-To: <CAHk-=wgcDUd-vGTTBN8UQJN7OyiDWvJy6udg3O0BFodkut1EkQ@mail.gmail.com>
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
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-08-05 16:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 10:22 [GIT PULL] arm64 updates for 5.20 Will Deacon
2022-08-01 17:51 ` pr-tracker-bot
2022-08-01 19:24 ` Linus Torvalds
2022-08-02 9:00 ` Will Deacon
2022-08-02 14:55 ` Linus Torvalds
2022-08-05 16:00 ` Will Deacon [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=20220805160034.GA29654@willie-the-truck \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=torvalds@linux-foundation.org \
/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