From: Jonathan Corbet <corbet@lwn.net>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-doc@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Linux Trace Kernel <linux-trace-kernel@vger.kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Tom Zanussi <zanussi@kernel.org>
Subject: Re: [PATCH] tracing: Documentation: Update histogram-design.rst for fn() handling
Date: Thu, 09 Apr 2026 09:59:17 -0600 [thread overview]
Message-ID: <87tstk9lbe.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260409115200.45883a07@gandalf.local.home>
Steven Rostedt <rostedt@goodmis.org> writes:
> On Thu, 09 Apr 2026 08:47:14 -0600
> Jonathan Corbet <corbet@lwn.net> wrote:
>
>> Steven Rostedt <rostedt@goodmis.org> writes:
>>
>> > Hi Jon,
>> >
>> > Can you take this through your tree?
>>
>> Somehow it fell through a crack in my inbox, but I have, finally, done
>> that. Sorry for the delay.
>
> Thanks, it has happened to me too often but not as much when I started
> using patchwork. Is there a patchwork monitoring linux-doc? If not, I
> highly recommend it. I stopped missing almost all patches when I started
> managing patches with patchwork. The few times I missed patches was when I
> accidentally incorrectly changed the status of a patch. But that's usually
> due to my own negligence and not simply because it was lost in my INBOX.
No patchwork ... but there is a *massive* pile of stuff that lands on
linux-doc that I'm not meant to touch. I think that "b4 review" might
be my way forward here.
Thanks,
jon
next prev parent reply other threads:[~2026-04-09 15:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 23:17 [PATCH] tracing: Documentation: Update histogram-design.rst for fn() handling Steven Rostedt
2026-03-05 16:03 ` Steven Rostedt
2026-03-05 16:12 ` Jonathan Corbet
2026-04-09 14:47 ` Jonathan Corbet
2026-04-09 15:52 ` Steven Rostedt
2026-04-09 15:59 ` Jonathan Corbet [this message]
2026-04-09 16:20 ` Steven Rostedt
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=87tstk9lbe.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@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