linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Jean THOMAS <virgule@jeanthomas.me>
Cc: devicetree@vger.kernel.org,
	~postmarketos/upstreaming@lists.sr.ht,
	linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
	petr.vorel@gmail.com, konradybcio@gmail.com
Subject: Re: [PATCH v2 1/2] arm64: dts: msm8992-lg-bullhead: Place LG Bullhead generic code into a DTSI file
Date: Mon, 31 Jan 2022 23:20:05 -0600	[thread overview]
Message-ID: <164369277342.3095904.5357867603310330864.b4-ty@linaro.org> (raw)
In-Reply-To: <20211201231832.188634-1-virgule@jeanthomas.me>

On Thu, 2 Dec 2021 00:18:31 +0100, Jean THOMAS wrote:
> This patch puts the generic code common across all hardware revisions
> into a DTSI file.
> 
> It also prefixes the DTS filename with the vendor name, to follow the
> naming convention used by other DTS files.
> 
> Changes since v1:
>  - Added "model" property to the DTS file
> 
> [...]

Applied, thanks!

[1/2] arm64: dts: msm8992-lg-bullhead: Place LG Bullhead generic code into a DTSI file
      commit: 3f99518c6f6520ad0fd14d862d54ee12f16156b4
[2/2] arm64: dts: msm8992-lg-bullhead: Add support for LG Bullhead rev 1.0
      commit: cd4bd4704ec8cff3d045493e2130c7095bbabf78

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

      parent reply	other threads:[~2022-02-01  5:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-01 23:18 [PATCH v2 1/2] arm64: dts: msm8992-lg-bullhead: Place LG Bullhead generic code into a DTSI file Jean THOMAS
2021-12-01 23:18 ` [PATCH v2 2/2] arm64: dts: msm8992-lg-bullhead: Add support for LG Bullhead rev 1.0 Jean THOMAS
2021-12-03 21:51   ` Petr Vorel
2021-12-03 21:50 ` [PATCH v2 1/2] arm64: dts: msm8992-lg-bullhead: Place LG Bullhead generic code into a DTSI file Petr Vorel
2022-01-13 20:38 ` Petr Vorel
2022-02-01  5:20 ` 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=164369277342.3095904.5357867603310330864.b4-ty@linaro.org \
    --to=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konradybcio@gmail.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=petr.vorel@gmail.com \
    --cc=virgule@jeanthomas.me \
    --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;
as well as URLs for NNTP newsgroup(s).