From: Paolo Abeni <pabeni@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: kuba@kernel.org, davem@davemloft.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Networking for v6.19-rc2
Date: Fri, 19 Dec 2025 09:36:06 +0100 [thread overview]
Message-ID: <cdee0c7e-9029-4b6c-8f7d-62c565bd6e90@redhat.com> (raw)
In-Reply-To: <CAHk-=whWLgrQjmVJk1bR14-7p9sc1wr1YvzsB=pxMTvxuhHDQw@mail.gmail.com>
On 12/18/25 9:04 PM, Linus Torvalds wrote:
> On Fri, 19 Dec 2025 at 05:56, Paolo Abeni <pabeni@redhat.com> wrote:
>>
>> I have a question WRT the next PR (for rc3). The usual schedule is quite
>> unfortunate (25 is the important day here) and I'll be able to process a
>> limited number of patches in between. I'm wondering if postponing such
>> net PR to Tue 30 would be ok for you?
>
> Oh, absolutely. Please don't think our rules are so black-and-white
> that a few days around xmas would ever be a problem.
>
> I'm planning on doing an rc8 for this release anyway, just because I
> expect people to lose at least a week due to the whole holiday season.
>
> The only really hard rule for the kernel is the "no regression" one.
> Any other rules we should be flexible about - they may need an
> explanation, but they shouldn't be seen as some kind of "set in stone"
> thing.
>
> And "it's the holidays, we're all busy with real life" is a perfectly
> good explanation.
Thank you! I'll send the PR on Tue 30. Likely it will be smaller than
usual, but it should include some relevant stuff.
Cheer,
Paolo
next prev parent reply other threads:[~2025-12-19 8:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 17:48 [GIT PULL] Networking for v6.19-rc2 Paolo Abeni
2025-12-18 17:56 ` Paolo Abeni
2025-12-18 20:04 ` Linus Torvalds
2025-12-19 8:36 ` Paolo Abeni [this message]
2025-12-18 20:40 ` pr-tracker-bot
2025-12-19 10:14 ` patchwork-bot+netdevbpf
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=cdee0c7e-9029-4b6c-8f7d-62c565bd6e90@redhat.com \
--to=pabeni@redhat.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox