public inbox for linux-trace-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Joel Fernandes <joel@joelfernandes.org>
Cc: Huang Yiwei <quic_hyiwei@quicinc.com>,
	mhiramat@kernel.org, mark.rutland@arm.com, mcgrof@kernel.org,
	keescook@chromium.org, j.granados@samsung.com,
	mathieu.desnoyers@efficios.com, corbet@lwn.net,
	linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, linux-doc@vger.kernel.org,
	quic_bjorande@quicinc.com, quic_tsoni@quicinc.com,
	quic_satyap@quicinc.com, quic_aiquny@quicinc.com,
	kernel@quicinc.com, Ross Zwisler <zwisler@google.com>
Subject: Re: [PATCH v4] tracing: Support to dump instance traces by ftrace_dump_on_oops
Date: Thu, 8 Feb 2024 04:36:59 -0500	[thread overview]
Message-ID: <20240208043659.7476b3a1@rorschach.local.home> (raw)
In-Reply-To: <497fdb48-9fce-444e-8d51-2073a37f697d@joelfernandes.org>

On Thu, 8 Feb 2024 04:26:30 -0500
Joel Fernandes <joel@joelfernandes.org> wrote:

> > And for this patchset, shall I fix the typo and resend again? Thanks.  
> 
> That is fine with me but it is up to tracing maintainers. ;-)

The rest of the patch looks good to me. Please send a v5 with the typo
fix and I'll try to get it into the next merge window.

Thanks,

-- Steve

      reply	other threads:[~2024-02-08  9:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-06  9:46 [PATCH v4] tracing: Support to dump instance traces by ftrace_dump_on_oops Huang Yiwei
2024-02-07 10:24 ` Joel Fernandes
2024-02-07 11:14   ` Steven Rostedt
2024-02-07 14:13     ` Joel Fernandes
2024-02-08  9:22       ` Huang Yiwei
2024-02-08  9:26         ` Joel Fernandes
2024-02-08  9:36           ` 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=20240208043659.7476b3a1@rorschach.local.home \
    --to=rostedt@goodmis.org \
    --cc=corbet@lwn.net \
    --cc=j.granados@samsung.com \
    --cc=joel@joelfernandes.org \
    --cc=keescook@chromium.org \
    --cc=kernel@quicinc.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mcgrof@kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=quic_aiquny@quicinc.com \
    --cc=quic_bjorande@quicinc.com \
    --cc=quic_hyiwei@quicinc.com \
    --cc=quic_satyap@quicinc.com \
    --cc=quic_tsoni@quicinc.com \
    --cc=zwisler@google.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