linux-kernel - Re: [GIT PULL] RISC-V Patches for the 5.16 Merge Window, Part 1

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: <mhng-6cc11053-b031-4ee5-875f-fa18095839db@palmer-ri-x1c9>
Date:   Fri, 12 Nov 2021 15:12:30 -0800 (PST)
From:   Palmer Dabbelt <palmer@...belt.com>
To:     schwab@...ux-m68k.org
CC:     Linus Torvalds <torvalds@...ux-foundation.org>,
        linux-kernel@...r.kernel.org, linux-riscv@...ts.infradead.org
Subject:     Re: [GIT PULL] RISC-V Patches for the 5.16 Merge Window, Part 1

On Fri, 12 Nov 2021 14:22:54 PST (-0800), schwab@...ux-m68k.org wrote:
> On Nov 12 2021, Palmer Dabbelt wrote:
>
>> I wasn't planning on sending anything else for the merge window.
>
> Not even the KBUILD_EXTMOD build fix?

Sorry, I hadn't seen that one.  I found some bugs in my test suite when 
getting it to run on the new machines so I've got some new failures I'm 
working through, which is sort of blocking up everything right now.  
Everything in this PR was tested the old way so I'm confident in it, but 
I usually do a merge with Linus' tree and test that before sending a PR.  
In hindsight it might have been better to skip that this time around, 
given all the headaches getting things up and running, but it's too late 
for that now.

I'd like to get back on a more solid footing before trying to pick up 
more stuff -- I guess that's a pretty trivial fix, but anything in the 
build system can run into wrinkles (also looks like it was broken in 
5.15, so it'll have to get backported).