From: Steven Rostedt <rostedt@goodmis.org>
To: Manivannan Sadhasivam <mani@kernel.org>
Cc: Shawn Lin <shawn.lin@rock-chips.com>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-rockchip@lists.infradead.org, linux-pci@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v5 0/3] PCI Controller event and LTSSM tracepoint support
Date: Mon, 6 Apr 2026 11:08:29 -0400 [thread overview]
Message-ID: <20260406110829.12f3e445@gandalf.local.home> (raw)
In-Reply-To: <u2dh2os5qyuuv636uwzttvohfyics7tvqiobheftjzdnuegq33@n77svn2nlqu2>
On Sat, 4 Apr 2026 22:23:32 +0530
Manivannan Sadhasivam <mani@kernel.org> wrote:
> On Wed, Mar 25, 2026 at 09:58:29AM +0800, Shawn Lin wrote:
> >
> > This patch-set adds new pci controller event and LTSSM tracepoint used by host drivers
> > which provide LTSSM trace functionality. The first user is pcie-dw-rockchip with a 256
> > Bytes FIFO for recording LTSSM transition.
> >
>
> Steve, could you please take a look at the tracing part?
I already have but didn't say anything because I didn't find anything ;-)
Anyway, for the tracing part:
Reviewed-by: Steven Rostedt (Google) <rostedt@goodmis.org>
-- Steve
next prev parent reply other threads:[~2026-04-06 15:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 1:58 [PATCH v5 0/3] PCI Controller event and LTSSM tracepoint support Shawn Lin
2026-03-25 1:58 ` [PATCH v5 1/3] PCI: trace: Add PCI controller LTSSM transition tracepoint Shawn Lin
2026-03-26 7:13 ` Anand Moon
2026-03-25 1:58 ` [PATCH v5 2/3] Documentation: tracing: Add PCI controller event documentation Shawn Lin
2026-03-25 1:58 ` [PATCH v5 3/3] PCI: dw-rockchip: Add pcie_ltssm_state_transition trace support Shawn Lin
2026-03-26 7:13 ` Anand Moon
2026-04-04 16:53 ` [PATCH v5 0/3] PCI Controller event and LTSSM tracepoint support Manivannan Sadhasivam
2026-04-06 15:08 ` Steven Rostedt [this message]
2026-04-07 14:43 ` Manivannan Sadhasivam
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=20260406110829.12f3e445@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=bhelgaas@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mani@kernel.org \
--cc=shawn.lin@rock-chips.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