Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Bjorn Andersson <andersson@kernel.org>
To: Andy Gross <agross@kernel.org>, Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Luca Weiss <luca.weiss@fairphone.com>,
	Konrad Dybcio <konrad.dybcio@linaro.org>
Cc: phone-devel@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-msm@vger.kernel.org,
	~postmarketos/upstreaming@lists.sr.ht,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v2 0/2] Enable remaining I2C busses on sm7225-fairphone-fp4
Date: Mon, 13 Feb 2023 14:23:04 -0800	[thread overview]
Message-ID: <167632698310.557014.13955392492218965629.b4-ty@kernel.org> (raw)
In-Reply-To: <20230213-fp4-more-i2c-v2-0-1c459c572f80@fairphone.com>

On Mon, 13 Feb 2023 15:46:29 +0100, Luca Weiss wrote:
> The first patch consolidate the two different styles where the status
> property is placed in the dts, and the second patch enables all the I2C
> busses used on the phone even if no subnode is added yet.
> 
> 

Applied, thanks!

[1/2] arm64: dts: qcom: sm7225-fairphone-fp4: move status property down
      commit: 65aedb0b48c09595065c81722d9cca53760f7220
[2/2] arm64: dts: qcom: sm7225-fairphone-fp4: enable remaining i2c busses
      commit: 574f2ffd45dc786dc443c5e11ea477420ffa5f52

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

      parent reply	other threads:[~2023-02-13 22:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-13 14:46 [PATCH v2 0/2] Enable remaining I2C busses on sm7225-fairphone-fp4 Luca Weiss
2023-02-13 14:46 ` [PATCH v2 1/2] arm64: dts: qcom: sm7225-fairphone-fp4: move status property down Luca Weiss
2023-02-13 14:46 ` [PATCH v2 2/2] arm64: dts: qcom: sm7225-fairphone-fp4: enable remaining i2c busses Luca Weiss
2023-02-13 22:23 ` 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=167632698310.557014.13955392492218965629.b4-ty@kernel.org \
    --to=andersson@kernel.org \
    --cc=agross@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=luca.weiss@fairphone.com \
    --cc=phone-devel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --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