From: Sudeep Holla <sudeep.holla@arm.com>
To: linux-arm-kernel@lists.infradead.org,
Cristian Marussi <cristian.marussi@arm.com>,
linux-kernel@vger.kernel.org
Cc: Sudeep Holla <sudeep.holla@arm.com>
Subject: Re: [PATCH] firmware: arm_scmi: Add delayed response status check
Date: Wed, 9 Jun 2021 21:46:34 +0100 [thread overview]
Message-ID: <162327154478.2648287.13789567557699425300.b4-ty@arm.com> (raw)
In-Reply-To: <20210608103056.3388-1-cristian.marussi@arm.com>
On Tue, 8 Jun 2021 11:30:56 +0100, Cristian Marussi wrote:
> A successfully received delayed response could anyway report a failure at
> the protocol layer in the message status field.
>
> Add a check also for this error condition.
Applied to sudeep.holla/linux (master), thanks!
[1/1] firmware: arm_scmi: Add delayed response status check
https://git.kernel.org/sudeep.holla/c/f1748b1ee1
--
Regards,
Sudeep
prev parent reply other threads:[~2021-06-09 20:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 10:30 [PATCH] firmware: arm_scmi: Add delayed response status check Cristian Marussi
2021-06-09 20:46 ` Sudeep Holla [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=162327154478.2648287.13789567557699425300.b4-ty@arm.com \
--to=sudeep.holla@arm.com \
--cc=cristian.marussi@arm.com \
--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).