From: Bjorn Andersson <andersson@kernel.org>
To: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Aleksandrs Vinarskis <alex.vinarskis@gmail.com>
Cc: Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bryan.Kemp@dell.com, tudor.laurentiu.oss@gmail.com,
tephan.gerhold@linaro.org, johan+linaro@kernel.org
Subject: Re: [PATCH v1 0/2] X1E Dell XPS 9345 Improvements 1
Date: Thu, 24 Oct 2024 09:59:28 -0500 [thread overview]
Message-ID: <172978197055.296432.9446476589955050893.b4-ty@kernel.org> (raw)
In-Reply-To: <20241016202253.9677-1-alex.vinarskis@gmail.com>
On Wed, 16 Oct 2024 22:15:47 +0200, Aleksandrs Vinarskis wrote:
> First round of improvements.
>
> * Add experimentally discovered edp enable gpio. Drop panel info, as it is
> now documented in [1]
> * Add Johan Hovold's fix for nvme regulator
>
> [1] https://lore.kernel.org/all/CAD=FV=Wu3vaY4Rtw4OZwgAf_b44JpDsKJhUa-EXiuu1hn3aJoQ@mail.gmail.com/
>
> [...]
Applied, thanks!
[1/2] arm64: dts: qcom: x1e80100-dell-xps13-9345: route edp-panel enable gpio
commit: 4e9b7787f80ae366f8a62a5a28955e134e522cc8
[2/2] arm64: dts: qcom: x1e80100-dell-xps13-9345: fix nvme regulator boot glitch
commit: 06d6fe987bda731b7c6619495aebedf638d37f2d
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2024-10-24 14:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 20:15 [PATCH v1 0/2] X1E Dell XPS 9345 Improvements 1 Aleksandrs Vinarskis
2024-10-16 20:15 ` [PATCH v1 1/2] arm64: dts: qcom: x1e80100-dell-xps13-9345: route edp-panel enable gpio Aleksandrs Vinarskis
2024-10-16 20:15 ` [PATCH v1 2/2] arm64: dts: qcom: x1e80100-dell-xps13-9345: fix nvme regulator boot glitch Aleksandrs Vinarskis
2024-10-18 9:25 ` Johan Hovold
2024-10-17 16:26 ` [PATCH v1 0/2] X1E Dell XPS 9345 Improvements 1 Rob Herring (Arm)
2024-10-24 14:59 ` 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=172978197055.296432.9446476589955050893.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=Bryan.Kemp@dell.com \
--cc=alex.vinarskis@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=johan+linaro@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=robh@kernel.org \
--cc=tephan.gerhold@linaro.org \
--cc=tudor.laurentiu.oss@gmail.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