From: Jonathan Corbet <corbet@lwn.net>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Tom Zanussi <zanussi@kernel.org>,
Artem Bityutskiy <dedekind1@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: trace: fix event state structure name
Date: Tue, 8 Dec 2020 10:21:12 -0700 [thread overview]
Message-ID: <20201208102112.2f0dccf9@lwn.net> (raw)
In-Reply-To: <20201207181914.370d4016@gandalf.local.home>
On Mon, 7 Dec 2020 18:19:14 -0500
Steven Rostedt <rostedt@goodmis.org> wrote:
> On Fri, 06 Nov 2020 14:47:46 -0600
> Tom Zanussi <zanussi@kernel.org> wrote:
>
> > Hi Artem,
> >
> > On Wed, 2020-11-04 at 14:21 +0200, Artem Bityutskiy wrote:
> > > From: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
> > >
> > > The documentation refers to a non-existent 'struct synth_trace_state'
> > > structure. The correct name is 'struct synth_event_trace_state'.
> > >
> > > In other words, this patch is a mechanical substitution:
> > > s/synth_trace_state/synth_event_trace_state/g
> > >
> > > Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
> >
> > Thanks for fixing this!
> >
> > Reviewed-by: Tom Zanussi <zanussi@kernel.org>
> >
>
> Jon,
>
> Can you take this patch?
>
> Acked-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
This wasn't sent to me, of course, so I was about to go digging into the
archive...until I realized I could just feed this email to b4 and
everything just happens by magic. How did we ever get by before b4?
Anyway...applied :)
Thanks,
jon
prev parent reply other threads:[~2020-12-08 17:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 12:21 [PATCH] docs: trace: fix event state structure name Artem Bityutskiy
2020-11-06 20:39 ` Steven Rostedt
2020-11-06 20:47 ` Tom Zanussi
2020-12-07 23:19 ` Steven Rostedt
2020-12-08 17:21 ` Jonathan Corbet [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=20201208102112.2f0dccf9@lwn.net \
--to=corbet@lwn.net \
--cc=dedekind1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=zanussi@kernel.org \
/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