From: Cristian Marussi <cristian.marussi@arm.com>
To: Roland Dreier <rolanddreier@rivian.com>
Cc: Sudeep Holla <sudeep.holla@kernel.org>,
Cristian Marussi <cristian.marussi@arm.com>,
arm-scmi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] firmware: arm_scmi: Protect xfer->async_done with xfer->lock
Date: Thu, 13 Aug 2026 11:14:28 +0100 [thread overview]
Message-ID: <an2ZBM0LGFT139j3@pluto> (raw)
In-Reply-To: <20260812224311.904964-1-rolanddreier@rivian.com>
On Wed, Aug 12, 2026 at 10:43:05PM +0000, Roland Dreier wrote:
> Asynchronous SCMI commands are completed by a delayed response. The RX
Hi,
> path signals the response with complete(xfer->async_done). Unlike
[snip]
>
> --
> *CONFIDENTIALITY NOTE:* This electronic message (including any attachments)
> may contain information that is privileged, confidential, and proprietary.
> If you are not the intended recipient, you are hereby notified that any
> disclosure, copying, distribution, or use of the information contained
> herein (including any reliance thereon) is strictly prohibited. If you
> received this electronic message in error, please immediately reply to the
> sender that you have received this communication and destroy the material
> in its entirety, whether in electronic or hard copy format. Although Rivian
> has taken reasonable precautions to ensure no viruses are present in this
> email, Rivian accepts no responsibility for any loss or damage arising from
> the use of this email or attachments.
...not so much to review with this footer...please drop it an repost
Thanks,
Cristian
prev parent reply other threads:[~2026-08-13 10:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-12 22:43 [PATCH 1/2] firmware: arm_scmi: Protect xfer->async_done with xfer->lock Roland Dreier
2026-08-12 22:43 ` [PATCH 2/2] firmware: arm_scmi: Don't reuse raw xfers with async_done still armed Roland Dreier
2026-08-13 10:14 ` Cristian Marussi [this message]
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=an2ZBM0LGFT139j3@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=rolanddreier@rivian.com \
--cc=sudeep.holla@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.