From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH 0/4] input: use devm_pm_set_wake_irq
Date: Mon, 26 Oct 2026 17:56:20 -0700 [thread overview]
Message-ID: <at_2lPLNBh_CQKOh@google.com> (raw)
In-Reply-To: <20250205-input-cleanup-v1-0-9758898ff8cb@nxp.com>
On Wed, Feb 05, 2025 at 08:45:13AM +0800, Peng Fan (OSS) wrote:
> This is a pick-up of patch 2-5 from patchset [1]
>
> Since devm_pm_set_wake_irq is in 6.14, so resend the input parts.
>
> [1] https://lore.kernel.org/all/CAJZ5v0jb=0c5m=FeA-W-aG30H4706Ay_xCHTsiC1S-7MuGxqTQ@mail.gmail.com/#r
>
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
> ---
> Peng Fan (4):
> input: keyboard: ep93xx_keypad: Use devm_pm_set_wake_irq
> input: keyboard: omap4_keypad: Use devm_pm_set_wake_irq
> input: misc: nxp-bbnsm-pwrkey: Use resource managed API to simplify code
> input: touchscreen: ti_am335x_tsc: Use resource managed API to simplify code
Applied with minor changes to patch #4, thank you.
--
Dmitry
prev parent reply other threads:[~2026-10-27 0:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-05 0:45 [PATCH 0/4] input: use devm_pm_set_wake_irq Peng Fan (OSS)
2025-02-05 0:45 ` [PATCH 1/4] input: keyboard: ep93xx_keypad: Use devm_pm_set_wake_irq Peng Fan (OSS)
2025-02-05 0:45 ` [PATCH 2/4] input: keyboard: omap4_keypad: " Peng Fan (OSS)
2025-02-05 0:45 ` [PATCH 3/4] input: misc: nxp-bbnsm-pwrkey: Use resource managed API to simplify code Peng Fan (OSS)
2025-02-05 0:45 ` [PATCH 4/4] input: touchscreen: ti_am335x_tsc: " Peng Fan (OSS)
2025-03-04 1:51 ` [PATCH 0/4] input: use devm_pm_set_wake_irq Peng Fan
2026-10-27 0:56 ` Dmitry Torokhov [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=at_2lPLNBh_CQKOh@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.