From: Cristian Marussi <cristian.marussi@arm.com>
To: Nikunj Kela <quic_nkela@quicinc.com>
Cc: Cristian Marussi <cristian.marussi@arm.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, arm-scmi@vger.kernel.org,
sudeep.holla@arm.com, james.quinlan@broadcom.com,
f.fainelli@gmail.com, vincent.guittot@linaro.org,
etienne.carriere@st.com, peng.fan@oss.nxp.com,
michal.simek@amd.com, quic_sibis@quicinc.com, ptosi@google.com,
dan.carpenter@linaro.org, souvik.chakravarty@arm.com,
Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH v3 6/9] firmware: arm_scmi: Make SMC transport a standalone driver
Date: Thu, 1 Aug 2024 20:21:36 +0100 [thread overview]
Message-ID: <ZqvgQMXXPa6_aFAR@pluto> (raw)
In-Reply-To: <04d0cf9a-dca8-4952-88fd-f7979a22602f@quicinc.com>
On Thu, Aug 01, 2024 at 11:46:03AM -0700, Nikunj Kela wrote:
>
> On 7/30/2024 6:33 AM, Cristian Marussi wrote:
> > Make SCMI SMC transport a standalone driver that can be optionally
> > loaded as a module.
> >
> > CC: Peng Fan <peng.fan@nxp.com>
> > CC: Nikunj Kela <quic_nkela@quicinc.com>
> > Signed-off-by: Cristian Marussi <cristian.marussi@arm.com>
> > ---
>
> Tested-by: Nikunj Kela <quic_nkela@quicinc.com>
>
> Tested this series on Qualcomm SA8255p(to be upstreamed) platform that
> uses Qualcomm SMC transport.
>
Thanks a lot for testing again this series, Nikunj !
Cristian
next prev parent reply other threads:[~2024-08-01 19:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 13:33 [PATCH v3 0/9] Make SCMI transport as standalone drivers Cristian Marussi
2024-07-30 13:33 ` [PATCH v3 1/9] firmware: arm_scmi: Fix double free in OPTEE transport Cristian Marussi
2024-07-30 14:37 ` Peng Fan
2024-07-30 13:33 ` [PATCH v3 2/9] firmware: arm_scmi: Introduce setup_shmem_iomap Cristian Marussi
2024-07-30 13:33 ` [PATCH v3 3/9] firmware: arm_scmi: Introduce packet handling helpers Cristian Marussi
2024-07-30 13:33 ` [PATCH v3 4/9] firmware: arm_scmi: Add support for standalone transport drivers Cristian Marussi
2024-07-30 13:33 ` [PATCH v3 5/9] firmware: arm_scmi: Make MBOX transport a standalone driver Cristian Marussi
2024-08-06 13:12 ` Sudeep Holla
2024-08-06 14:59 ` Cristian Marussi
2024-07-30 13:33 ` [PATCH v3 6/9] firmware: arm_scmi: Make SMC " Cristian Marussi
2024-08-01 18:46 ` Nikunj Kela
2024-08-01 19:21 ` Cristian Marussi [this message]
2024-07-30 13:33 ` [PATCH v3 7/9] firmware: arm_scmi: Make OPTEE " Cristian Marussi
2024-07-31 6:12 ` Krzysztof Kozlowski
2024-08-01 19:22 ` Cristian Marussi
2024-07-30 13:33 ` [PATCH v3 8/9] firmware: arm_scmi: Make VirtIO " Cristian Marussi
2024-07-31 6:11 ` Krzysztof Kozlowski
2024-08-01 19:25 ` Cristian Marussi
2024-07-30 13:33 ` [PATCH v3 9/9] firmware: arm_scmi: Remove legacy transport-layer code Cristian Marussi
2024-07-31 13:12 ` [PATCH v3 0/9] Make SCMI transport as standalone drivers Peng Fan
2024-08-01 18:41 ` Nikunj Kela
2024-08-06 16:47 ` Florian Fainelli
2024-08-06 17:01 ` 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=ZqvgQMXXPa6_aFAR@pluto \
--to=cristian.marussi@arm.com \
--cc=arm-scmi@vger.kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=etienne.carriere@st.com \
--cc=f.fainelli@gmail.com \
--cc=james.quinlan@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.com \
--cc=ptosi@google.com \
--cc=quic_nkela@quicinc.com \
--cc=quic_sibis@quicinc.com \
--cc=souvik.chakravarty@arm.com \
--cc=sudeep.holla@arm.com \
--cc=vincent.guittot@linaro.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).