From: Shawn Guo <shawn.guo@linaro.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: devicetree@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-arm-msm@vger.kernel.org, Shawn Guo <shawn.guo@linaro.org>
Subject: [PATCH 0/4] Fix number of pins in 'gpio-ranges'
Date: Wed, 3 Mar 2021 11:31:02 +0800 [thread overview]
Message-ID: <20210303033106.549-1-shawn.guo@linaro.org> (raw)
The fixes are split per SoC to ease the stable kernel pick-up.
Shawn Guo (4):
arm64: dts: qcom: sdm845: fix number of pins in 'gpio-ranges'
arm64: dts: qcom: sm8150: fix number of pins in 'gpio-ranges'
arm64: dts: qcom: sm8250: fix number of pins in 'gpio-ranges'
arm64: dts: qcom: sm8350: fix number of pins in 'gpio-ranges'
arch/arm64/boot/dts/qcom/sdm845.dtsi | 2 +-
arch/arm64/boot/dts/qcom/sm8150.dtsi | 2 +-
arch/arm64/boot/dts/qcom/sm8250.dtsi | 2 +-
arch/arm64/boot/dts/qcom/sm8350.dtsi | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
--
2.17.1
next reply other threads:[~2021-03-03 21:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 3:31 Shawn Guo [this message]
2021-03-03 3:31 ` [PATCH 1/4] arm64: dts: qcom: sdm845: fix number of pins in 'gpio-ranges' Shawn Guo
2021-03-05 21:43 ` Bjorn Andersson
2021-03-06 1:28 ` Shawn Guo
2021-03-06 1:56 ` Bjorn Andersson
2021-03-06 8:00 ` Shawn Guo
2021-03-10 18:22 ` Bjorn Andersson
2021-03-11 1:19 ` Shawn Guo
2021-03-11 16:53 ` Bjorn Andersson
2021-03-11 23:09 ` Shawn Guo
2021-03-11 23:17 ` Bjorn Andersson
2021-03-15 16:11 ` Linus Walleij
2021-03-03 3:31 ` [PATCH 2/4] arm64: dts: qcom: sm8150: " Shawn Guo
2021-03-03 3:31 ` [PATCH 3/4] arm64: dts: qcom: sm8250: " Shawn Guo
2021-03-03 3:31 ` [PATCH 4/4] arm64: dts: qcom: sm8350: " Shawn Guo
2021-03-11 23:40 ` [PATCH 0/4] Fix " patchwork-bot+linux-arm-msm
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=20210303033106.549-1-shawn.guo@linaro.org \
--to=shawn.guo@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@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).