From: Alex Elder <elder@linaro.org>
To: stable@vger.kernel.org
Cc: kuba@kernel.org, bjorn.andersson@linaro.org,
quic_clew@quicinc.com, quic_deesin@quicinc.com,
swboyd@chromium.org, elder@kernel.org,
gregkh@linuxfoundation.org
Subject: [PATCH v2 0/3] net: ipa: backport for v5.15.y
Date: Thu, 14 Apr 2022 10:21:28 -0500 [thread overview]
Message-ID: <20220414152131.713724-1-elder@linaro.org> (raw)
This series is a back-port for stable branch version 5.15 *only*.
The IPA patches have already been applied to v5.16.y, and they are
not required for versions prior to 5.15.
There was a missing prerequisite commit that prevented building the
code successfully when back-porting to v5.15 was first attempted.
That commit has been added to the front of this series. All three
commits otherwise cherry-pick cleanly.
Version 2 just adds my sign-off on the first patch (and is rebased).
-Alex
Alex Elder (2):
dt-bindings: net: qcom,ipa: add optional qcom,qmp property
net: ipa: request IPA register values be retained
Deepak Kumar Singh (1):
soc: qcom: aoss: Expose send for generic usecase
.../devicetree/bindings/net/qcom,ipa.yaml | 6 +++
drivers/net/ipa/ipa_power.c | 52 ++++++++++++++++++
drivers/net/ipa/ipa_power.h | 7 +++
drivers/net/ipa/ipa_uc.c | 5 ++
drivers/soc/qcom/qcom_aoss.c | 54 ++++++++++++++++++-
include/linux/soc/qcom/qcom_aoss.h | 38 +++++++++++++
6 files changed, 161 insertions(+), 1 deletion(-)
create mode 100644 include/linux/soc/qcom/qcom_aoss.h
--
2.32.0
next reply other threads:[~2022-04-14 15:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 15:21 Alex Elder [this message]
2022-04-14 15:21 ` [PATCH v2 1/3] soc: qcom: aoss: Expose send for generic usecase Alex Elder
2022-04-14 15:21 ` [PATCH v2 2/3] dt-bindings: net: qcom,ipa: add optional qcom,qmp property Alex Elder
2022-04-14 15:21 ` [PATCH v2 3/3] net: ipa: request IPA register values be retained Alex Elder
2022-04-15 10:30 ` [PATCH v2 0/3] net: ipa: backport for v5.15.y Greg KH
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=20220414152131.713724-1-elder@linaro.org \
--to=elder@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=elder@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=quic_clew@quicinc.com \
--cc=quic_deesin@quicinc.com \
--cc=stable@vger.kernel.org \
--cc=swboyd@chromium.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