From: Shree Ramamoorthy <s-ramamoorthy@ti.com>
To: Mark Brown <broonie@kernel.org>
Cc: <lgirdwood@gmail.com>, <aaro.koskinen@iki.fi>,
<andreas@kemnade.info>, <khilman@baylibre.com>,
<rogerq@kernel.org>, <tony@atomide.com>,
<linux-omap@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<m-leonard@ti.com>, <praneeth@ti.com>
Subject: Re: [PATCH v4 0/4] Add TI TPS65214 & TPS65215 Regulator Support
Date: Fri, 28 Feb 2025 11:30:43 -0600 [thread overview]
Message-ID: <40bd4297-ad4f-41e2-8bd3-e6c11dc40a17@ti.com> (raw)
In-Reply-To: <131466cc-dc54-4251-82f7-5ec9e9c20f26@sirena.org.uk>
Hi Mark,
On 2/26/2025 4:40 PM, Mark Brown wrote:
> On Wed, Feb 12, 2025 at 01:11:25PM -0600, Shree Ramamoorthy wrote:
>
>> Dependencies:
>> - Patches 2 & 3 depend on https://lore.kernel.org/all/20250206173725.386720-5-s-ramamoorthy@ti.com/
>> - Patch 4 depends on https://lore.kernel.org/all/20250206173725.386720-6-s-ramamoorthy@ti.com/
> These all appear to be in the MFD tree without a tag to pull from or
> anything so I can't apply any of this stuff until after the merge
> window. I'm not clear why they weren't sent as part of the MFD series?
> You should probably resend copying Lee.
I wasn't sure if the MFD + entire regulator patches could be sent in the same series, so this is good to know!
I will resend a v5 Regulator series with Lee cc'd asking if he can take the series if you give the patches an ACK when ready.
next prev parent reply other threads:[~2025-02-28 17:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 19:11 Shree Ramamoorthy
2025-02-12 19:11 ` [PATCH v4 1/4] regulator: tps65219: Update struct names Shree Ramamoorthy
2025-02-12 19:11 ` [PATCH v4 2/4] regulator: tps65219: Add support for TPS65215 regulator resources Shree Ramamoorthy
2025-02-12 19:11 ` [PATCH v4 3/4] regulator: tps65219: Add support for TPS65215 Regulator IRQs Shree Ramamoorthy
2025-02-12 19:11 ` [PATCH v4 4/4] regulator: tps65219: Add TI TPS65214 Regulator Support Shree Ramamoorthy
2025-02-26 22:40 ` [PATCH v4 0/4] Add TI TPS65214 & TPS65215 " Mark Brown
2025-02-28 17:30 ` Shree Ramamoorthy [this message]
2025-02-28 22:17 ` Mark Brown
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=40bd4297-ad4f-41e2-8bd3-e6c11dc40a17@ti.com \
--to=s-ramamoorthy@ti.com \
--cc=aaro.koskinen@iki.fi \
--cc=andreas@kemnade.info \
--cc=broonie@kernel.org \
--cc=khilman@baylibre.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=m-leonard@ti.com \
--cc=praneeth@ti.com \
--cc=rogerq@kernel.org \
--cc=tony@atomide.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
Powered by JetHome