From: Cristian Marussi <cristian.marussi@arm.com>
To: Philip Radford <philip.radford@arm.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, arm-scmi@vger.kernel.org,
sudeep.holla@arm.com, cristian.marussi@arm.com,
luke.parkin@arm.com
Subject: Re: [PATCH 2/4] firmware: arm_scmi: Add xfer_inflight counter
Date: Thu, 26 Jun 2025 12:15:15 +0100 [thread overview]
Message-ID: <aF0rw1D6QXGrCdmU@pluto> (raw)
In-Reply-To: <20250619122004.3705976-3-philip.radford@arm.com>
On Thu, Jun 19, 2025 at 12:20:02PM +0000, Philip Radford wrote:
> Added an xfer_inflight counter to the debug_counters struct
> to record the current number of inflight xfers
>
Hi,
nitpick around the commite message.
Add a counter to the debug_counters struct to record the current number
of outstanding inflight xfers.
...note also the full-stop :P
With this:
Reviewed-by: Cristian Marussi <cristian.marussi@arm.com>
Thanks,
Cristian
next prev parent reply other threads:[~2025-06-26 11:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-19 12:20 [PATCH 0/4] firmware: arm_scmi: Add xfer inflight debug and trace Philip Radford
2025-06-19 12:20 ` [PATCH 1/4] firmware: arm_scmi: Add debug decrement counter Philip Radford
2025-06-19 14:32 ` Dan Carpenter
2025-06-26 11:10 ` Cristian Marussi
2025-06-19 12:20 ` [PATCH 2/4] firmware: arm_scmi: Add xfer_inflight counter Philip Radford
2025-06-26 11:15 ` Cristian Marussi [this message]
2025-06-19 12:20 ` [PATCH 3/4] include: trace: Add inflight_xfer counter tracepoint Philip Radford
2025-06-19 12:20 ` [PATCH 4/4] firmware: arm_scmi: Add new inflight tracing functionality Philip Radford
2025-06-19 14:37 ` Dan Carpenter
2025-06-26 11:17 ` Cristian Marussi
2025-06-20 8:46 ` [PATCH 0/4] firmware: arm_scmi: Add xfer inflight debug and trace Peng Fan
2025-06-20 9:27 ` Philip Radford
2025-06-24 4:22 ` Peng Fan
2025-06-26 11:37 ` Cristian Marussi
2025-06-30 2:00 ` Peng Fan
2025-06-26 11:18 ` Cristian Marussi
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=aF0rw1D6QXGrCdmU@pluto \
--to=cristian.marussi@arm.com \
--cc=arm-scmi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luke.parkin@arm.com \
--cc=philip.radford@arm.com \
--cc=sudeep.holla@arm.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).