From: Mark Brown <broonie@kernel.org>
To: Saravana Kannan <saravanak@google.com>
Cc: Marek Szyprowski <m.szyprowski@samsung.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Bjorn Andersson <andersson@kernel.org>,
Sudeep Holla <sudeep.holla@arm.com>,
Tony Lindgren <tony@atomide.com>,
Doug Anderson <dianders@chromium.org>,
Guenter Roeck <linux@roeck-us.net>,
Luca Weiss <luca.weiss@fairphone.com>,
kernel-team@android.com, linux-kernel@vger.kernel.org
Subject: Re: [RFC v1 0/4] Simplify regulator supply resolution code by offloading to driver core
Date: Tue, 21 Feb 2023 22:52:52 +0000 [thread overview]
Message-ID: <Y/VLREM7n+wstHbn@sirena.org.uk> (raw)
In-Reply-To: <CAGETcx-UcVnDw-FJAPeA1mLpPno4OE3AAv4WsfP852zOdKqPCw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 325 bytes --]
On Tue, Feb 21, 2023 at 02:36:52PM -0800, Saravana Kannan wrote:
> Thanks for testing it Marek! I don't want people to spend more time
> testing this before I hear Mark/Liam's thoughts. So, let's hold off
> for now.
My main thought right now is that I'm not going to think about it
too hard if it doesn't work correctly...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-02-21 22:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230218083300eucas1p28c7c584877b8914a3b88904690be82f6@eucas1p2.samsung.com>
2023-02-18 8:32 ` Saravana Kannan
2023-02-18 8:32 ` [RFC v1 1/4] regulator: core: Add regulator devices to bus instead of class Saravana Kannan
2023-02-18 8:32 ` [RFC v1 2/4] regulator: core: Add sysfs class backward compatibility Saravana Kannan
2023-02-22 17:47 ` Mark Brown
2023-02-18 8:32 ` [RFC v1 3/4] regulator: core: Probe regulator devices Saravana Kannan
2023-02-22 17:50 ` Mark Brown
2023-02-18 8:32 ` [RFC v1 4/4] regulator: core: Move regulator supply resolving to the probe function Saravana Kannan
2023-02-22 22:51 ` Mark Brown
2023-02-18 8:36 ` [RFC v1 0/4] Simplify regulator supply resolution code by offloading to driver core Saravana Kannan
2023-02-18 8:54 ` Greg Kroah-Hartman
2023-02-20 9:01 ` Marek Szyprowski
2023-02-21 22:36 ` Saravana Kannan
2023-02-21 22:52 ` Mark Brown [this message]
2023-02-22 3:13 ` Saravana Kannan
2023-02-22 14:54 ` Mark Brown
2023-02-22 7:15 ` Marek Szyprowski
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=Y/VLREM7n+wstHbn@sirena.org.uk \
--to=broonie@kernel.org \
--cc=andersson@kernel.org \
--cc=dianders@chromium.org \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-team@android.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=luca.weiss@fairphone.com \
--cc=m.szyprowski@samsung.com \
--cc=saravanak@google.com \
--cc=sudeep.holla@arm.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
all inboxes | Powered by JetHome®