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

[Mark Brown]

On Tue, Feb 17, 2026 at 06:12:38PM +0000, Steven French wrote:

> This large series has been in ksmbd-for-next for about a week but had
> been going through testing for longer, and most of the changes are
> fairly narrowly scoped to the new smbdirect (rdma) module and much are
> small incremental patches for the moving to common code for smbdirect
> (from server and client).  There are at least three devs independently
> running (xfstests etc) tests against it and test results have looked
> good so far.  Most of this smbdirect work is being driven by Metze so
> adding him to cc:

Given that we're in the merge window now you should really only be
putting things in -next that are bugfixes or are otherwise intended to
go in during the merge window, when the merge window opened it looks
like the tip of tree for ksmbd was 164cacd0ba38 ("smb: server: correct
value for smb_direct_max_fragmented_recv_size") which has already been
merged so this is all new stuff.  New development should ideally wait
until -rc1, if it's going to be sent in the merge window the expectation
is that it should have been visible for testing in -next prior to the
merge window opening.

Now I look again the counts got confused by one of the intermediate
branches not being properly handled, the actual counts should
(hopefully) be:

120 amdgpu
143 phy-next
146 ksmbd
255 perf
297 char-misc

or excluding things that were already in -next when the merge window
opened:

39 drm-xe
42 net
63 mmc
69 amdgpu
146 ksmbd

(mmc had a build issue that had kept it out of -next and got the pull
dropped).  Sorry about the noise with the counts earlier.

Attachment: signature.asc
Description: PGP signature