Re: Policy regarding linux-next only changes
From: Tetsuo Handa
Date: Sun Jul 05 2026 - 10:17:51 EST
On 2026/07/05 21:06, Mark Brown wrote:
> On Sat, Jul 04, 2026 at 02:06:43PM +0200, Miguel Ojeda wrote:
>> On Sat, Jul 4, 2026 at 12:15窶ッPM Tetsuo Handa
>
>> For the latter, it simply says that sometimes debugging patches have
>> been added in the past to linux-next. It doesn't say it was done
>> unilaterally. (And even if it did, it is just a third-party document).
>
> ...
>
>> I understand it may be nice to use such resources, but the solution is
>> to talk to both sides, as you do in that thread. From what I see, they
>> even offered to add a mailing list for those patches:
>
> Right, this seems to be something where people need to talk more. It
> does seem like there's real communication problems that need to be
> addressed, it looks like some progress is being made thanks to this
> thread.
Yes, thanks to this thread. There is real communication problems.
Developers / maintainers are too busy to continue threads on my patches.
Let's see several examples.
Example 1: (not a problem with linux-next only patch, but a communication problem)
Linus's "None of this makes any sense." comment at
https://lkml.kernel.org/r/CAHk-=wjmFiptPgaPx9vY3RG=rqO452UmOAPb1y_f9GQBtuJVjg@xxxxxxxxxxxxxx
made Mikulas to say "I don't know what else to do." at
https://lkml.kernel.org/r/290bd5eb-9638-53ce-3c71-23b996d6ba54@xxxxxxxxxx , causing
https://lkml.kernel.org/r/329e1951-0704-4d90-aeeb-ffc7123f4262@xxxxxxxxxxxxxxxxxxx and
https://lkml.kernel.org/r/9a05e50c-75c1-4452-b40f-f5a8b487f3ed@xxxxxxxxxxxxxxxxxxx to stall.
We need clarification from Linus or response from Mikulas.
Example 2: (a problem with moving from linux-next only patch to networking patch, but a communication problem)
I responded to Jakub's "Have you see netdev_hold() / netdev_put() ?" comment at
https://lkml.kernel.org/r/20260325192214.133ffaaf@xxxxxxxxxx but got no response.
I need clarification or response from Jakub. If some core maintainer asks network
people "Let's update all existing dev_put()/dev_hold() users to use netdev_put()/
netdev_hold()", some progress would be made. No progress as long as no response.
Example 3: (a problem with linux-next only patch, but a communication problem)
I responded to Al's "Not a peep in the logs, breakage still there" comment at
https://lkml.kernel.org/r/ebceac56-6a65-4918-b47c-1fb87aa66989@xxxxxxxxxxxxxxxxxxx
but got no response. Therefore, I sent an updated version
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit?id=3ae78a69d3a9a4ad1d3b267324bd742654f40965
to linux-next, and I am currently waiting for syzbot to reproduce this problem.