Subject: Re: -next status as at week one of the v7.0 merge window

From: Krzysztof Kozlowski <[email-masked]>
Date: Tue, 17 Feb 2026 13:20:48 +0100

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