Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Bjorn Andersson <andersson@kernel.org>
To: Konrad Dybcio <konradybcio@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Sibi Sankar <quic_sibis@quicinc.com>,
	Abel Vesa <abel.vesa@linaro.org>
Cc: Johan Hovold <johan@kernel.org>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] arm64: dts: x1e001de-devkit: USB retimers related fixes
Date: Tue, 13 May 2025 21:46:38 +0100	[thread overview]
Message-ID: <174716895383.39748.703153321484020943.b4-ty@kernel.org> (raw)
In-Reply-To: <20250318-x1e001de-devkit-dts-fix-retimer-gpios-v1-0-1c092f630b0c@linaro.org>


On Tue, 18 Mar 2025 17:50:33 +0200, Abel Vesa wrote:
> These fixes align all the USB retimer related nodes on the Devkit with the
> CRD and T14s.
> 
> This patchset is based on Johan's:
> https://lore.kernel.org/all/20250318074907.13903-1-johan+linaro@kernel.org/
> 
> 
> [...]

Applied, thanks!

[1/2] arm64: dts: qcom: x1e001de-devkit: Describe USB retimers resets pin configs
      commit: f76fdcd2550991c854a698a9f881b1579455fc0a
[2/2] arm64: dts: qcom: x1e001de-devkit: Fix pin config for USB0 retimer vregs
      commit: 635d0c8edf26994dc1dcbc09add9423aa61869b0

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

      parent reply	other threads:[~2025-05-13 20:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-18 15:50 [PATCH 0/2] arm64: dts: x1e001de-devkit: USB retimers related fixes Abel Vesa
2025-03-18 15:50 ` [PATCH 1/2] arm64: dts: qcom: x1e001de-devkit: Describe USB retimers resets pin configs Abel Vesa
2025-04-04 23:08   ` Konrad Dybcio
2025-03-18 15:50 ` [PATCH 2/2] arm64: dts: qcom: x1e001de-devkit: Fix pin config for USB0 retimer vregs Abel Vesa
2025-04-04 23:08   ` Konrad Dybcio
2025-04-11 11:58     ` Johan Hovold
2025-04-22 11:14       ` Abel Vesa
2025-05-13 20:46 ` 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=174716895383.39748.703153321484020943.b4-ty@kernel.org \
    --to=andersson@kernel.org \
    --cc=abel.vesa@linaro.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=johan@kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_sibis@quicinc.com \
    --cc=robh@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