linux-kernel - Re: [PATCH] tracing: Fix several comment spelling mistakes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20251121150446.13d24840@gandalf.local.home>
Date: Fri, 21 Nov 2025 15:04:46 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Maurice Hieronymus <mhi@...lbox.org>
Cc: mingo@...hat.com, linux-kernel@...r.kernel.org,
 linux-trace-devel@...r.kernel.org, Masami Hiramatsu <mhiramat@...nel.org>
Subject: Re: [PATCH] tracing: Fix several comment spelling mistakes

On Fri, 21 Nov 2025 19:45:01 +0100
Maurice Hieronymus <mhi@...lbox.org> wrote:

> Hi Steven, hi Ingo,

Note, Ingo is no longer one of the tracing subsystem maintainers. That is
now Masami Hiramatsu. Please update your MAINTAINERS file.

> 
> I've just realized, that I send my patch against trace/master whereas
> the current development seems to happen on trace/for-next.
> 
> I'm new to the mailing list, so please bear with me. Two question arise
> for me:
> 
> Are you even interested in spelling fixes like I did below?

I'll take spelling fixes, but they are very low on the priority list. I'll
usually pull them in after all other patches have been processed in a
release cycle.

> 
> And if yes, does all the new development happens in general on
> trace/for-next?

The trace/for-next branch is for new development of the general tracing
code. But other code may go through other topic branches. There's a
latency/for-next branch that handles the runtime verifier.

Best to break up the patches per file, otherwise they may not apply
correctly.


> 
> Thanks a lot for a quick reply. If I get a positive answer from you I
> will resend my patch on the correct branch.
> 

> > diff --git a/kernel/trace/rv/Kconfig b/kernel/trace/rv/Kconfig
> > index 831779607e84..b76ba1aad0a0 100644
> > --- a/kernel/trace/rv/Kconfig
> > +++ b/kernel/trace/rv/Kconfig
> > @@ -45,7 +45,7 @@ config RV_MON_WWNR
> >  	help
> >  	  Enable wwnr (wakeup while not running) sample monitor, this is a
> >  	  sample monitor that illustrates the usage of per-task monitor.
> > -	  The model is borken on purpose: it serves to test reactors.
> > +	  The model is broken on purpose: it serves to test reactors.

This is not a spelling fix. "borken" is a common word used in the kernel
community.

-- Steve

> >  
> >  	  For further information, see:
> >  	    Documentation/trace/rv/monitor_wwnr.rst