From: Cristian Marussi <cristian.marussi@arm.com>
To: Philip Radford <Philip.Radford@arm.com>
Cc: Dan Carpenter <dan.carpenter@linaro.org>,
cristian.marussi@arm.com, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, arm-scmi@vger.kernel.org
Subject: Re: [PATCH 4/4] firmware: arm_scmi: Add new inflight tracing functionality
Date: Thu, 19 Jun 2025 16:42:10 +0100 [thread overview]
Message-ID: <aFQv0rwS3PwyTeG7@pluto> (raw)
In-Reply-To: <PAWPR08MB99669F0D3EB80C4ACAA90DFA897DA@PAWPR08MB9966.eurprd08.prod.outlook.com>
On Thu, Jun 19, 2025 at 04:13:57PM +0100, Philip Radford wrote:
> > -----Original Message-----
> > From: Dan Carpenter <dan.carpenter@linaro.org>
> > Sent: Thursday, June 19, 2025 3:38 PM
> > To: Philip Radford <Philip.Radford@arm.com>
>
> Hi,
>
> > Cc: linux-kernel@vger.kernel.org; linux-arm-kernel@lists.infradead.org; arm-
> > scmi@vger.kernel.org; Sudeep Holla <Sudeep.Holla@arm.com>; Cristian
> > Marussi <Cristian.Marussi@arm.com>; Luke Parkin <Luke.Parkin@arm.com>
> > Subject: Re: [PATCH 4/4] firmware: arm_scmi: Add new inflight tracing
> > functionality
Hi Phil,
please reply to all the recipient of the original mail-thread when answering a
review, so we remain on the list. (mutt -> g .. I think :P)
(I added the CCs to this)
Thanks,
Cristian
next parent reply other threads:[~2025-06-19 15:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <PAWPR08MB99669F0D3EB80C4ACAA90DFA897DA@PAWPR08MB9966.eurprd08.prod.outlook.com>
2025-06-19 15:42 ` Cristian Marussi [this message]
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 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
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=aFQv0rwS3PwyTeG7@pluto \
--to=cristian.marussi@arm.com \
--cc=Philip.Radford@arm.com \
--cc=arm-scmi@vger.kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).