From: Krzysztof Kozlowski <krzk@kernel.org>
To: Shree Ramamoorthy <s-ramamoorthy@ti.com>,
aaro.koskinen@iki.fi, andreas@kemnade.info, khilman@baylibre.com,
rogerq@kernel.org, tony@atomide.com, lee@kernel.org,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: m-leonard@ti.com, praneeth@ti.com, christophe.jaillet@wanadoo.fr
Subject: Re: [PATCH v1 0/1] Add TI TPS65214 PMIC MFD Support
Date: Fri, 17 Jan 2025 10:23:28 +0100 [thread overview]
Message-ID: <85cfecd0-644d-4035-96bb-5b7752aecb04@kernel.org> (raw)
In-Reply-To: <20250116223915.430263-1-s-ramamoorthy@ti.com>
On 16/01/2025 23:39, Shree Ramamoorthy wrote:
> TPS65214 is a Power Management Integrated Circuit (PMIC) that has
> significant register map overlap with TPS65215 and TPS65219. The series
> introduces TPS65214 and adds the device to the multi-PMIC support driver.
>
> This follow-up series is dependent on:
> Commit d23b7176df4a ("regulator: dt-bindings: Add TI TPS65214 PMIC bindings")
What is this commit? Which tree? Recent next does not have it.
The other thread said it depends on this patch, so how do you see it
being merged? A depends on B, B depends on A. If A gets merged first:
broken kernel. If B gets merged first: broken kernel? So what does this
dependency and commit even mean?
Best regards,
Krzysztof
prev parent reply other threads:[~2025-01-17 9:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 22:39 [PATCH v1 0/1] Add TI TPS65214 PMIC MFD Support Shree Ramamoorthy
2025-01-16 22:39 ` [PATCH v1 1/1] mfd: tps65214: Add support for TI TPS65214 PMIC Shree Ramamoorthy
2025-01-17 9:22 ` Krzysztof Kozlowski
2025-01-17 9:23 ` Krzysztof Kozlowski [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=85cfecd0-644d-4035-96bb-5b7752aecb04@kernel.org \
--to=krzk@kernel.org \
--cc=aaro.koskinen@iki.fi \
--cc=andreas@kemnade.info \
--cc=christophe.jaillet@wanadoo.fr \
--cc=khilman@baylibre.com \
--cc=lee@kernel.org \
--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=s-ramamoorthy@ti.com \
--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