Re: Policy regarding linux-next only changes

[Boqun Feng <boqun@kernel.org>]

On Sat, Jul 25, 2026 at 07:38:25PM +0900, Tetsuo Handa wrote:
> On 2026/07/25 18:38, Miguel Ojeda wrote:
> > No, what prevents you from debugging is that, from what you say,
> > nobody is giving enough compute resources for your task.
> 
> OK. Let's go back to https://lkml.kernel.org/r/bc3703bd-65ee-4182-a742-56603d9b9bac@I-love.SAKURA.ne.jp .
> 
> If I were able to use a kernel config option which minimizes impact for others,
> the technical problem for my task will be solved.
> 
> But including what kernel config options (or kernel command line parameters) I can use, there
> hardly is a discussion from developers / maintainers. The last discussion was 6 years ago:
> 

As I said [1], the reposting was stopped 6 years ago, and no one could
read other's mind to know whether it's still worth discussing.

>   https://lkml.kernel.org/r/20200413063317.7164-1-penguin-kernel@I-love.SAKURA.ne.jp
>   https://lkml.kernel.org/r/20200307135822.3894-1-penguin-kernel@I-love.SAKURA.ne.jp
> 
> Can we resume this discussion so that we can minimize surprising other developers / maintainers?
> 

Yes, resending the patches, talking about it in a conference, or giving
people a heads-up when planning to queue it via linux-next is the way to
resume the discussion. Could you please do any of these?

[1]: https://lore.kernel.org/lkml/akpxYEF2ZI7p1zn3@MacBook-0RXW5/

Regards,
Boqun