public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Mickaël Salaün" <mic@digikod.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Günther Noack" <gnoack@google.com>,
	"Matthieu Buffet" <matthieu@buffet.re>,
	"Tingmao Wang" <m@maowtm.org>,
	linux-kernel@vger.kernel.org,
	linux-security-module@vger.kernel.org
Subject: Re: [GIT PULL] Landlock fix for v6.19-rc6
Date: Fri, 16 Jan 2026 15:18:15 +0100	[thread overview]
Message-ID: <20260116.feegh2ohQuae@digikod.net> (raw)
In-Reply-To: <CAHk-=wgPRijTr7fZQNs9pxbhRLBVQGdE7ceZDwQFP53MXjRBxg@mail.gmail.com>

On Thu, Jan 15, 2026 at 03:09:34PM -0800, Linus Torvalds wrote:
> On Thu, 15 Jan 2026 at 13:47, Mickaël Salaün <mic@digikod.net> wrote:
> >
> > This PR fixes TCP handling, tests, documentation, non-audit elided code,
> > and minor cosmetic changes.
> 
> This seems significantly bigger than what you sent for the whole merge
> window for the Landlock code.
> 
> The merge window pull was - ignoring tests - 4 files changed, 59
> insertions(+), 17 deletions(-).
> 
> I want more explanations for why I'm suddenly getting more alleged
> fixes than I got any development and why this shouldn't wait until the
> next merge window.
> 
> Because honestly, this just all seems out of place.

There are indeed relatively more line changes because the related
commits are fixes for different kernel versions, not specifically v6.19
but also v6.15 (type issue), v6.7 (TCP fix), and it required to move a
lot of lines (including a lot of comments) for a theoretically small
fix.  In fact, the last merge window pull was mostly about fixes too
(which were on time for the merge window, but otherwise I would have
sent them as this one).

The other commits are documentation/comment fixes (including another
chunk of moved lines, which appears as kernel code diff), tests fixes or
minor cleanup.  I can postpone these commits but because they don't
directly impact the kernel, I wanted to group all fixes and minor
non-kernel changes together to have a clean PR for the next merge
window.  Please let me know what you prefer.

 Mickaël

  reply	other threads:[~2026-01-16 14:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-15 21:47 [GIT PULL] Landlock fix for v6.19-rc6 Mickaël Salaün
2026-01-15 23:09 ` Linus Torvalds
2026-01-16 14:18   ` Mickaël Salaün [this message]
2026-01-18 23:19     ` Linus Torvalds
2026-01-19 13:54 ` pr-tracker-bot

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=20260116.feegh2ohQuae@digikod.net \
    --to=mic@digikod.net \
    --cc=gnoack@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=m@maowtm.org \
    --cc=matthieu@buffet.re \
    --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