linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Andersson <andersson@kernel.org>
To: LKML <linux-kernel@vger.kernel.org>,
	yunlong.jia@ecs.corp-partner.google.com
Cc: henrysun@google.com, devicetree@vger.kernel.org,
	moragues@chromium.org, agross@kernel.org,
	Douglas Anderson <dianders@chromium.org>,
	robh+dt@kernel.org, linux-arm-msm@vger.kernel.org,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Konrad Dybcio <konrad.dybcio@somainline.org>
Subject: Re: (subset) [PATCH v3 1/2] dt-bindings: arm: qcom: Document additional skus for sc7180 pazquel360
Date: Mon, 17 Oct 2022 22:15:21 -0500	[thread overview]
Message-ID: <166606235849.3553294.10700447109437637515.b4-ty@kernel.org> (raw)
In-Reply-To: <20220901024827.v3.1.I3aa360986c0e7377ea5e96c116f014ff1ab8c968@changeid>

On Thu, 1 Sep 2022 02:49:57 +0000, Yunlong Jia wrote:
> pazquel360 is an extension project based on pazquel.
> We create 3 sku on pazquel360:
>    sku 20 for LTE with physical SIM _and_ eSIM and WiFi
>    sku 21 for WiFi only
>    sku 22 for LTE with only a physical SIM
>  Both sku20 and sku22 are LTE SKUs.
>  One has the eSIM stuffed and one doesn't.
>  There is a single shared device tree for the two.
> 
> [...]

Applied, thanks!

[1/2] dt-bindings: arm: qcom: Document additional skus for sc7180 pazquel360
      commit: 185d192d0a7b565a24b3f7456a2f84f169ab087a
[2/2] arm64: dts: qcom: Add sc7180-pazquel360
      commit: 2f72a4f54cdb4fd0ebea9a2dea65756d3e676be2

Best regards,
-- 
Bjorn Andersson <andersson@kernel.org>

  parent reply	other threads:[~2022-10-18  3:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-01  2:49 [PATCH v3 1/2] dt-bindings: arm: qcom: Document additional skus for sc7180 pazquel360 Yunlong Jia
2022-09-01  2:49 ` [PATCH v3 2/2] arm64: dts: qcom: Add sc7180-pazquel360 Yunlong Jia
2022-09-06 22:26 ` [PATCH v3 1/2] dt-bindings: arm: qcom: Document additional skus for sc7180 pazquel360 Doug Anderson
2022-10-18  3:15 ` Bjorn Andersson [this message]
2022-10-20 22:36   ` (subset) " Doug Anderson

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=166606235849.3553294.10700447109437637515.b4-ty@kernel.org \
    --to=andersson@kernel.org \
    --cc=agross@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dianders@chromium.org \
    --cc=henrysun@google.com \
    --cc=konrad.dybcio@somainline.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=moragues@chromium.org \
    --cc=robh+dt@kernel.org \
    --cc=yunlong.jia@ecs.corp-partner.google.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).