From: Lee Jones <lee@kernel.org>
To: Benjamin Bara <bbara93@gmail.com>
Cc: Wolfram Sang <wsa@kernel.org>,
rafael.j.wysocki@intel.com, dmitry.osipenko@collabora.com,
peterz@infradead.org, jonathanh@nvidia.com,
richard.leitner@linux.dev, treding@nvidia.com,
linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org,
linux-tegra@vger.kernel.org,
Benjamin Bara <benjamin.bara@skidata.com>
Subject: Re: [PATCH v6 4/5] mfd: tps6586x: use devm-based power off handler
Date: Thu, 18 May 2023 10:43:40 +0100 [thread overview]
Message-ID: <20230518094340.GC404509@google.com> (raw)
In-Reply-To: <20230327-tegra-pmic-reboot-v6-4-af44a4cd82e9@skidata.com>
On Tue, 09 May 2023, Benjamin Bara wrote:
> From: Benjamin Bara <benjamin.bara@skidata.com>
>
> Convert the power off handler to a devm-based power off handler.
>
> Signed-off-by: Benjamin Bara <benjamin.bara@skidata.com>
> ---
> drivers/mfd/tps6586x.c | 29 +++++++++++++++++++++--------
> 1 file changed, 21 insertions(+), 8 deletions(-)
Do the 2 MFD patches depend on the others?
For my own reference (apply this as-is to your sign-off block):
Acked-for-MFD-by: Lee Jones <lee@kernel.org>
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2023-05-18 9:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-09 19:02 [PATCH v6 0/5] mfd: tps6586x: register restart handler Benjamin Bara
2023-05-09 19:02 ` [PATCH v6 1/5] kernel/reboot: emergency_restart: set correct system_state Benjamin Bara
2023-05-18 11:34 ` Dmitry Osipenko
2023-06-15 0:06 ` Nishanth Menon
2023-06-15 13:21 ` Francesco Dolcini
2023-06-15 14:39 ` Nishanth Menon
2023-05-09 19:03 ` [PATCH v6 2/5] i2c: core: run atomic i2c xfer when !preemptible Benjamin Bara
2023-05-18 11:34 ` Dmitry Osipenko
2023-06-15 0:05 ` Nishanth Menon
2023-05-09 19:03 ` [PATCH v6 3/5] kernel/reboot: add device to sys_off_handler Benjamin Bara
2023-05-18 11:39 ` Dmitry Osipenko
2023-05-09 19:03 ` [PATCH v6 4/5] mfd: tps6586x: use devm-based power off handler Benjamin Bara
2023-05-18 9:43 ` Lee Jones [this message]
2023-05-18 11:15 ` Benjamin Bara
2023-05-18 11:40 ` Dmitry Osipenko
2023-05-09 19:03 ` [PATCH v6 5/5] mfd: tps6586x: register restart handler Benjamin Bara
2023-05-18 9:44 ` Lee Jones
2023-05-18 11:48 ` Dmitry Osipenko
2023-07-12 3:40 ` Dmitry Osipenko
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=20230518094340.GC404509@google.com \
--to=lee@kernel.org \
--cc=bbara93@gmail.com \
--cc=benjamin.bara@skidata.com \
--cc=dmitry.osipenko@collabora.com \
--cc=jonathanh@nvidia.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rafael.j.wysocki@intel.com \
--cc=richard.leitner@linux.dev \
--cc=treding@nvidia.com \
--cc=wsa@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