linux-kernel - Re: [GIT PULL] Driver core updates for 6.4-rc1

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] [day] [month] [year] [list]

Date:   Fri, 28 Apr 2023 08:55:16 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Greg KH <gregkh@...uxfoundation.org>
Cc:     Nipun Gupta <nipun.gupta@....com>,
        Nikhil Agarwal <nikhil.agarwal@....com>,
        Catalin Marinas <catalin.marinas@....com>,
        Will Deacon <will@...nel.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        linux-kernel@...r.kernel.org,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        Saravana Kannan <saravanak@...gle.com>
Subject: Re: [GIT PULL] Driver core updates for 6.4-rc1

On Thu, Apr 27, 2023 at 10:12 PM Greg KH <gregkh@...uxfoundation.org> wrote:
>
> In the future, how do you want stuff like "when this is merged with that
> tree, something needs to be done" type of things to be pointed out?

Just having it pointed out is fine. I notice build errors on x86-64
myself, but other architectures get rather iffy. arm64 is the best of
the bunch, in that I *will* do the build test, it's just not as
timely.

If known merge issues get pointed out, I (a) know to look out for them
and (b) know that the trees involved actually were in linux-next and
people were paying attention.

It's usually not been a problem with your trees, particularly since
most of your stuff does build on x86. This whole CDX subsystem being
arm64-only is not great for build coverage.

               Linus