linux-kernel - Re: [GIT PULL] RISC-V updates for the v6.19 merge window (part two)

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: <736f7ecb-f1fd-5dec-9cb5-88e2d241eda3@kernel.org>
Date: Fri, 12 Dec 2025 19:26:16 -0700 (MST)
From: Paul Walmsley <pjw@...nel.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
cc: Paul Walmsley <pjw@...nel.org>, sfr@...b.auug.org.au, 
    akpm@...ux-foundation.org, linux-kernel@...r.kernel.org, 
    linux-riscv@...ts.infradead.org
Subject: Re: [GIT PULL] RISC-V updates for the v6.19 merge window (part
 two)

On Sat, 13 Dec 2025, Linus Torvalds wrote:

> On Fri, 12 Dec 2025 at 14:36, Paul Walmsley <pjw@...nel.org> wrote:
> >
> > Please pull this second and final set of RISC-V patches for the v6.19
> > merge window.  The primary addition in this pull request is support for
> > CFI in user processes.  This series has been around for almost two years.
> 
> It can damn well be around for another release then.
> 
> Because I'm really tired of these late pull requests. That's true in
> general, but it's particularly true when I've told people I'm
> traveling with a laptop. I was spending extra time the first week of
> the merge window to get things out of the way so that I would *not*
> have to deal with conflicts etc when on the road.
> 
> I appreciate people who send me a second pull request with *fixes* for
> the first one because they are starting to already react to bug
> reports. But your whole thing where you think you send me a first pull
> request and then a second one late in the merge window with more
> development is simply not ok.

It won't happen again.  Thanks for the feedback.  We'll get the CFI series 
early into linux-next for v6.20.

> Either it was ready to go early, or it's not ready to go at all. None
> of this "I have more presents for you".
> 
> The merge window is not for late development or for "Let's make extra
> work for Linus the last day of the merge window when he's on the road
> in a strange time zone"


Understood, and sorry for the noise,

- Paul