From: Bjorn Andersson <andersson@kernel.org>
To: linux-kernel@vger.kernel.org,
Raymond Hackley <raymondhackley@protonmail.com>
Cc: Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Stephan Gerhold <stephan@gerhold.net>,
Nikita Travkin <nikita@trvn.ru>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht
Subject: Re: [PATCH v3 0/3] arm64: dts: qcom: msm8916-samsung-fortuna: Add initial device trees
Date: Sat, 27 Jan 2024 20:17:25 -0600 [thread overview]
Message-ID: <170640822845.30820.4228813434034188940.b4-ty@kernel.org> (raw)
In-Reply-To: <20240120095715.13689-1-raymondhackley@protonmail.com>
On Sat, 20 Jan 2024 09:57:27 +0000, Raymond Hackley wrote:
> Samsung Galaxy Core Prime and Grand Prime are phones based on MSM8916.
> They are similar to the other Samsung devices based on MSM8916 with only a
> few minor differences.
>
> This initial commit adds support for:
> - fortuna3g (SM-G530H)
> - gprimeltecan (SM-G530W)
> - grandprimelte (SM-G530FZ)
> - rossa (SM-G360G)
>
> [...]
Applied, thanks!
[1/2] dt-bindings: qcom: Document new msm8916-samsung devices
commit: 80daa2fa2ff2ce01550713956a6f7e18bbbd3f7f
[2/2] arm64: dts: qcom: msm8916-samsung-fortuna: Add initial device trees
(no commit info)
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2024-01-28 2:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-20 9:57 [PATCH v3 0/3] arm64: dts: qcom: msm8916-samsung-fortuna: Add initial device trees Raymond Hackley
2024-01-20 9:57 ` [PATCH v3 1/2] dt-bindings: qcom: Document new msm8916-samsung devices Raymond Hackley
2024-01-20 9:57 ` [PATCH v3 2/2] arm64: dts: qcom: msm8916-samsung-fortuna: Add initial device trees Raymond Hackley
2024-01-28 0:47 ` Bjorn Andersson
2024-01-20 10:09 ` [PATCH v3 0/3] " Raymond Hackley
2024-01-28 2:17 ` Bjorn Andersson [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=170640822845.30820.4228813434034188940.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nikita@trvn.ru \
--cc=raymondhackley@protonmail.com \
--cc=robh+dt@kernel.org \
--cc=stephan@gerhold.net \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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