linux-kernel - Re: [GIT PULL] RISC-V Patches for the 5.20 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] [day] [month] [year] [list]

Message-ID: <mhng-7e789be2-ce2f-41e0-935e-d966cb93ff4a@palmer-mbp2014>
Date:   Fri, 12 Aug 2022 09:05:55 -0700 (PDT)
From:   Palmer Dabbelt <palmer@...osinc.com>
To:     ben.dooks@...ethink.co.uk
CC:     Linus Torvalds <torvalds@...ux-foundation.org>,
        linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject:     Re: [GIT PULL] RISC-V Patches for the 5.20 Merge Window, Part 1

On Mon, 08 Aug 2022 00:35:24 PDT (-0700), ben.dooks@...ethink.co.uk wrote:
> On 06/08/2022 00:36, Palmer Dabbelt wrote:
>> The following changes since commit 924cbb8cbe3460ea192e6243017ceb0ceb255b1b:
>>
>>    riscv: Improve description for RISCV_ISA_SVPBMT Kconfig symbol (2022-06-16 15:47:39 -0700)
>>
>> are available in the Git repository at:
>>
>>    git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git tags/riscv-for-linus-5.20-mw0
>>
>> for you to fetch changes up to ba6cfef057e1c594c456627aad81c2343fdb5d13:
>>
>>    riscv: enable Docker requirements in defconfig (2022-07-22 13:43:28 -0700)
>>
>> ----------------------------------------------------------------
>> RISC-V Patches for the 5.20 Merge Window, Part 1
>>
>> * Enabling the FPU is now a static_key.
>> * Improvements to the Svpbmt support.
>> * CPU topology bindings for a handful of systems.
>> * Support for systems with 64-bit hart IDs.
>> * Many settings have been enabled in the defconfig, including both
>>    support for the StarFive systems and many of the Docker requirements.
>>
>> There are also a handful of cleanups and improvements, like usual.
>>
>
> Hi, are some of mine and Connor's fixes planned for part2?

Yes, though maybe that's obvious given that a bunch of them are on 
for-next now...

I was hoping to send that this morning but I ran into a few snags.  If 
there's anything else missing just let me know, IRC is usually the best 
way to jump the queue for small stuff -- it kind of just gets buried 
otherwise.