From: Lee Jones <lee@kernel.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Lee Jones <lee@kernel.org>, Michael Walle <mwalle@kernel.org>
Cc: jcormier@criticallink.com, Job Sava <jsava@criticallink.com>,
linux-kernel@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: [PATCH v2 0/3] mfd: tps6594: add power button and power-off
Date: Wed, 03 Sep 2025 11:45:08 +0100 [thread overview]
Message-ID: <175689630841.2597045.5125819314695096057.b4-ty@kernel.org> (raw)
In-Reply-To: <20250826134631.1499936-1-mwalle@kernel.org>
On Tue, 26 Aug 2025 15:46:28 +0200, Michael Walle wrote:
> I took over the series from [1] since the original developer was an
> intern and is no longer with their former company.
>
> Changelog is in the individual patches. But the most prominent
> change is that the pin mux config is now read from the chip itself
> instead of having a DT property.
>
> [...]
Applied, thanks!
[1/3] input: tps6594-pwrbutton: Add power button functionality
commit: 170031ff27dd7a07fdedee7f3710a19dcdf889bd
[2/3] mfd: tps6594: add power button functionality
commit: d766ca01c208bdf0f36098607efe1e250ccf41c5
[3/3] mfd: tps6594: Add board power-off support
commit: 2215a87b02ad8d353cd3edebd1bed01db2458986
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2025-09-03 10:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-26 13:46 Michael Walle
2025-08-26 13:46 ` [PATCH v2 1/3] input: tps6594-pwrbutton: Add power button functionality Michael Walle
2025-08-26 13:46 ` [PATCH v2 2/3] mfd: tps6594: add " Michael Walle
2025-08-26 13:46 ` [PATCH v2 3/3] mfd: tps6594: Add board power-off support Michael Walle
2025-09-03 10:45 ` Lee Jones [this message]
2025-09-03 10:46 ` [PATCH v2 0/3] mfd: tps6594: add power button and power-off Lee Jones
2025-09-03 11:32 ` [GIT PULL] Immutable branch between MFD and Input due for the v6.18 merge window Lee Jones
2025-09-11 15:14 ` [GIT PULL v2] " Lee Jones
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=175689630841.2597045.5125819314695096057.b4-ty@kernel.org \
--to=lee@kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=jcormier@criticallink.com \
--cc=jsava@criticallink.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mwalle@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®