All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Walmsley <pjw@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Paul Walmsley <pjw@kernel.org>,
	sfr@canb.auug.org.au,  akpm@linux-foundation.org,
	linux-kernel@vger.kernel.org,  linux-riscv@lists.infradead.org
Subject: Re: [GIT PULL] RISC-V updates for the v6.19 merge window (part two)
Date: Fri, 12 Dec 2025 19:26:16 -0700 (MST)	[thread overview]
Message-ID: <736f7ecb-f1fd-5dec-9cb5-88e2d241eda3@kernel.org> (raw)
In-Reply-To: <CAHk-=wiBP2B788uvFxyiy38JvtTb_3HrbjABWkCyXf_Rxbo4vQ@mail.gmail.com>

On Sat, 13 Dec 2025, Linus Torvalds wrote:

> On Fri, 12 Dec 2025 at 14:36, Paul Walmsley <pjw@kernel.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

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

WARNING: multiple messages have this Message-ID (diff)
From: Paul Walmsley <pjw@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Paul Walmsley <pjw@kernel.org>,
	sfr@canb.auug.org.au,  akpm@linux-foundation.org,
	linux-kernel@vger.kernel.org,  linux-riscv@lists.infradead.org
Subject: Re: [GIT PULL] RISC-V updates for the v6.19 merge window (part two)
Date: Fri, 12 Dec 2025 19:26:16 -0700 (MST)	[thread overview]
Message-ID: <736f7ecb-f1fd-5dec-9cb5-88e2d241eda3@kernel.org> (raw)
In-Reply-To: <CAHk-=wiBP2B788uvFxyiy38JvtTb_3HrbjABWkCyXf_Rxbo4vQ@mail.gmail.com>

On Sat, 13 Dec 2025, Linus Torvalds wrote:

> On Fri, 12 Dec 2025 at 14:36, Paul Walmsley <pjw@kernel.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

  reply	other threads:[~2025-12-13  2:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-12  2:36 [GIT PULL] RISC-V updates for the v6.19 merge window (part two) Paul Walmsley
2025-12-12  2:36 ` Paul Walmsley
2025-12-12 17:56 ` Linus Torvalds
2025-12-12 17:56   ` Linus Torvalds
2025-12-13  2:26   ` Paul Walmsley [this message]
2025-12-13  2:26     ` Paul Walmsley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=736f7ecb-f1fd-5dec-9cb5-88e2d241eda3@kernel.org \
    --to=pjw@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.