From: Steven Rostedt <rostedt@goodmis.org>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH] fsi: Add trace events in initialization path
Date: Mon, 7 Feb 2022 11:48:13 -0500 [thread overview]
Message-ID: <20220207114813.3856554e@gandalf.local.home> (raw)
In-Reply-To: <20220207161640.35605-1-eajames@linux.ibm.com>
On Mon, 7 Feb 2022 10:16:40 -0600
Eddie James <eajames@linux.ibm.com> wrote:
> Add definitions for trace events to show the scanning flow.
>
> Signed-off-by: Eddie James <eajames@linux.ibm.com>
>
From a tracing point of view, I don't see anything wrong with this patch.
Reviewed-by: Steven Rostedt (Google) <rostedt@goodmis.org>
-- Steve
next prev parent reply other threads:[~2022-02-07 16:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 16:16 [PATCH] fsi: Add trace events in initialization path Eddie James
2022-02-07 16:48 ` Steven Rostedt [this message]
2022-02-21 9:09 ` Joel Stanley
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=20220207114813.3856554e@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-aspeed@lists.ozlabs.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