From: Nishanth Menon <nm@ti.com>
To: Tero Kristo <kristo@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Vignesh Raghavendra <vigneshr@ti.com>
Cc: Nishanth Menon <nm@ti.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Bjorn Andersson <quic_bjorande@quicinc.com>,
Arnd Bergmann <arnd@arndb.de>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next 0/2] arm64: dts: ti: Fixes for Beagleplay SD
Date: Thu, 30 Mar 2023 17:05:01 -0500 [thread overview]
Message-ID: <168021381989.189465.7612644484912733056.b4-ty@ti.com> (raw)
In-Reply-To: <20230330105921.3639185-1-vigneshr@ti.com>
Hi Vignesh Raghavendra,
On Thu, 30 Mar 2023 16:29:19 +0530, Vignesh Raghavendra wrote:
> Couple of fixups on top of ti-next branch:
>
> The SD supply on Beagle is really coming from PMIC LDO1 even though its
> controllable via GPIO, hence fix the DT accordingly, this also means
> PMIC regulator drivers need to be built-in to allow SD card rootfs
>
> Nishanth,
> Better to squash into respetive commits if possible
>
> [...]
I have fixed the following to branch ti-k3-dts-next and ti-k3-config-next on [1].
I had to rewrite history a bit here, but anyways..
Thank you!
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
[1] git://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
prev parent reply other threads:[~2023-03-30 22:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 10:59 Vignesh Raghavendra
2023-03-30 10:59 ` [PATCH 1/2] arm64: configs: defconfig: Make TPS65219 regulator built-in Vignesh Raghavendra
2023-03-30 10:59 ` [PATCH 2/2] arm64: dts: ti: k3-am625-beagleplay: Fixup SD card supply regulator Vignesh Raghavendra
2023-03-30 14:59 ` [PATCH -next 0/2] arm64: dts: ti: Fixes for Beagleplay SD Nishanth Menon
2023-03-30 22:05 ` Nishanth Menon [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=168021381989.189465.7612644484912733056.b4-ty@ti.com \
--to=nm@ti.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_bjorande@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.com \
--cc=will@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
all inboxes | Powered by JetHome®