linux-kernel - Re: [GIT PULL] arm64 updates for 5.20

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAHk-=wgcDUd-vGTTBN8UQJN7OyiDWvJy6udg3O0BFodkut1EkQ@mail.gmail.com>
Date:   Tue, 2 Aug 2022 07:55:38 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Will Deacon <will@...nel.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 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).

             Linus