From: Krzysztof Kozlowski <krzk@kernel.org>
To: Mark Brown <broonie@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Namjae Jeon <linkinjeon@kernel.org>,
Steve French <stfrench@microsoft.com>
Subject: Re: -next status as at week one of the v7.0 merge window
Date: Tue, 17 Feb 2026 13:20:48 +0100 [thread overview]
Message-ID: <9fd209e1-e9f7-446c-98cc-e8f3aa17077b@kernel.org> (raw)
In-Reply-To: <56867107-7db2-4c93-b8f4-f732fc780c35@sirena.org.uk>
On 16/02/2026 16:52, Mark Brown wrote:
> Hi Linus,
>
> Trees being held at old versions:
>
> mm-nomm-unstable next-20260213 (trivial -Werror thing from today)
>
> No trees have signoff problems.
>
> Merge summary:
>
> Non-merge commits (relative to Linus' tree): 2227
> 2029 files changed, 83194 insertions(+), 35136 deletions(-)
>
> Top 5 trees adding commits to -next:
>
> 146 ksmbd
And there is a bunch of warnings from LKP about ksmbd tree:
https://lore.kernel.org/all/?q=ksmbd+f%3Alkp%40intel.com
and looking here:
https://github.com/smfrench/smb3-kernel/commits/ksmbd-for-next/
I see entire page of commits "committed 11 hours ago", so this entire
work might have never been in the next for this cycle thus never
actually integration tested?
> 26 ntfs3
I think this tree was requested to be added just a day before, so might
have the same problem - lack of wider build exposure.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-02-17 12:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-16 15:52 -next status as at week one of the v7.0 merge window Mark Brown
2026-02-17 12:20 ` Krzysztof Kozlowski [this message]
2026-02-17 12:51 ` Mark Brown
2026-02-17 18:12 ` [EXTERNAL] " Steven French
2026-02-17 18:55 ` Mark Brown
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=9fd209e1-e9f7-446c-98cc-e8f3aa17077b@kernel.org \
--to=krzk@kernel.org \
--cc=broonie@kernel.org \
--cc=linkinjeon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=stfrench@microsoft.com \
--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