From: Jim Quinlan <jim2101024@gmail.com>
To: Sudeep Holla <sudeep.holla@arm.com>,
bcm-kernel-feedback-list@broadcom.com, jim2101024@gmail.com,
james.quinlan@broadcom.com
Cc: devicetree@vger.kernel.org (open list:OPEN FIRMWARE AND
FLATTENED DEVICE TREE BINDINGS),
linux-arm-kernel@lists.infradead.org (open list:SYSTEM CONTROL &
POWER/MANAGEMENT INTERFACE Mes...),
linux-kernel@vger.kernel.org (open list)
Subject: [PATCH v4 0/2] firmware: arm_scmi: Augment SMC/HVC to allow optional interrupt
Date: Tue, 22 Dec 2020 09:56:01 -0500 [thread overview]
Message-ID: <20201222145603.40192-1-jim2101024@gmail.com> (raw)
v4 -- s/message-serviced/a2p/ in the bindings commit message.
-- Changed author/s-o-b/committer email address as my company is now
appending boilerplate text to all outgoing emails.
v3 -- Changed interrupt name from "message-serviced" to "a2p" (RobH)
v2 -- Correct commit message, s/msg/message/, and remove extra WS on
"dt-bindings" commit (Sudeep)
-- Change interrupt name to "message-serviced", move irq assignent to end
of function. (Sudeep)
v1 -- original.
Jim Quinlan (2):
dt-bindings: arm: Add optional interrupt to smc/hvc SCMI transport
firmware: arm_scmi: Augment SMC/HVC to allow optional interrupt
.../devicetree/bindings/arm/arm,scmi.txt | 8 ++++
drivers/firmware/arm_scmi/smc.c | 38 ++++++++++++++++++-
2 files changed, 45 insertions(+), 1 deletion(-)
--
2.17.1
next reply other threads:[~2020-12-22 14:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-22 14:56 Jim Quinlan [this message]
2020-12-22 14:56 ` [PATCH v4 1/2] dt-bindings: arm: Add optional interrupt to smc/hvc SCMI transport Jim Quinlan
2020-12-23 2:48 ` Florian Fainelli
2021-01-03 16:40 ` Rob Herring
2020-12-22 14:56 ` [PATCH v4 2/2] firmware: arm_scmi: Augment SMC/HVC to allow optional interrupt Jim Quinlan
2020-12-23 3:37 ` Florian Fainelli
2021-01-05 17:35 ` Sudeep Holla
[not found] ` <CA+-6iNwnA+3kaHom3XRpTLOu_4QsHOmFiZ2M2=sA7Go-uADe1g@mail.gmail.com>
2021-01-05 18:32 ` Jim Quinlan
2021-01-06 9:30 ` Sudeep Holla
2021-01-06 14:33 ` Jim Quinlan
2021-01-04 14:57 ` [PATCH v4 0/2] " Jim Quinlan
2021-01-04 16:02 ` Sudeep Holla
2021-01-11 18:30 ` Sudeep Holla
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=20201222145603.40192-1-jim2101024@gmail.com \
--to=jim2101024@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=james.quinlan@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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).