linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: John Keeping <john@metanate.com>
Cc: linux-trace-devel@vger.kernel.org, linux-kernel@vger.kernel.org,
	Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH/RFC] tracing: make trace_marker{,_raw} stream-like
Date: Tue, 7 Dec 2021 09:03:47 -0500	[thread overview]
Message-ID: <20211207090347.15822d87@gandalf.local.home> (raw)
In-Reply-To: <Ya835b6JGrjBQCtF@donbot>

On Tue, 7 Dec 2021 10:31:15 +0000
John Keeping <john@metanate.com> wrote:

> Were you expecting more input from me on this?  The above sounded like
> "will be added for 5.16" but I don't see this change in v5.16-rc4 and
> the patch is still marked as "New" in patchwork [1]
> 
> [1] https://patchwork.kernel.org/project/linux-trace-devel/patch/20210909115734.3818711-1-john@metanate.com/

And that explains why I didn't add it :-(

The linux-trace-devel is mainly for user space tools, although some kernel
patches end up there too. Any patch that hits my inbox without Cc'ing
linux-trace-devel falls into my internal patchwork. I look at that one
first for kernel patches to add to my queue, and then I'll look at that
public one. I forgot about this conversation, and because the title of that
patch has RFC in it, I thought there would be another patch coming. I don't
add RFC patches generally, and forgot about this conversation.

Can you resend the patch to me, but remove the linux-trace-devel mailing
list (but still include linux-kernel).

Thanks!

-- Steve

      reply	other threads:[~2021-12-07 14:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-09 11:57 [PATCH/RFC] tracing: make trace_marker{,_raw} stream-like John Keeping
2021-09-09 12:35 ` Steven Rostedt
2021-12-07 10:31   ` John Keeping
2021-12-07 14:03     ` 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=20211207090347.15822d87@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=john@metanate.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-devel@vger.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).