linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Maurice Hieronymus <mhi@mailbox.org>
Cc: mingo@redhat.com, linux-kernel@vger.kernel.org,
	linux-trace-devel@vger.kernel.org,
	Masami Hiramatsu <mhiramat@kernel.org>
Subject: Re: [PATCH] tracing: Fix several comment spelling mistakes
Date: Fri, 21 Nov 2025 15:04:46 -0500	[thread overview]
Message-ID: <20251121150446.13d24840@gandalf.local.home> (raw)
In-Reply-To: <3716cf61-b1cc-43c6-84e3-cb4c62495549@mailbox.org>

On Fri, 21 Nov 2025 19:45:01 +0100
Maurice Hieronymus <mhi@mailbox.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

      reply	other threads:[~2025-11-21 20:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-16 21:03 [PATCH] tracing: Fix several comment spelling mistakes Maurice Hieronymus
2025-11-21 18:45 ` Maurice Hieronymus
2025-11-21 20:04   ` Steven Rostedt [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20251121150446.13d24840@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=mhi@mailbox.org \
    --cc=mhiramat@kernel.org \
    --cc=mingo@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).