Re: Policy regarding linux-next only changes

[Miguel Ojeda]

On Sat, Jul 25, 2026 at 5:44 AM Tetsuo Handa
<penguin-kernel@xxxxxxxxxxxxxxxxxxx> wrote:
>
> Excuse me, but what does "successfully unit tested" mean? Broken patches
> that do not build, or trigger oops by just "/bin/cat" _are_ arriving at
> linux-next tree, which in turn preventing continuous testing by syzbot.

Yes, there are mistakes in linux-next all the time, and those mistakes
take time away from maintainers. Which is why adding more unexpected
patches makes it worse.

But, really, that is not the question at hand -- you say:

  "my debug patches won't be able to find a route to linux-next, which
   in turn prevents us from debugging."

No, what prevents you from debugging is that, from what you say,
nobody is giving enough compute resources for your task.

linux-next is just a way to access some resources. Which may be OK or
not to do so, but clearly it was not in agreement by everyone nor in
alignment with what linux-next is supposed to be so far, and that is
what I pointed out, nothing else.

Cheers,
Miguel