From: Frank.Li@oss.nxp.com
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Dong Aisheng <aisheng.dong@nxp.com>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>, Frank Li <Frank.Li@nxp.com>
Cc: linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/2] input: fsl,scu-key: Add compatible string fsl,imx8qm-sc-key
Date: Tue, 14 Jul 2026 11:47:06 -0400 [thread overview]
Message-ID: <178404388197.1628554.1376903172807695440.b4-ty@b4> (raw)
In-Reply-To: <20251028-b4_qm_scu_key-v1-0-9732e92a5e83@nxp.com>
From: Frank Li <Frank.Li@nxp.com>
On Tue, 28 Oct 2025 16:01:27 -0400, Frank Li wrote:
> bindings: add fsl,imx8qm-sc-key.
> dts: add fsl,imx8qm-sc-key support.
Applied, thanks!
[1/2] dt-bindings: input: fsl,scu-key: Add compatible string fsl,imx8qm-sc-key
commit: df9b9d59586f3d8bdeba5b3c7b7ea68cb0302fb7
I picked it because it was missed since 2025 OCT and ping 2026 Jan and
fsl,scu-key.yaml was only used by imx/
[2/2] arm64: dts: imx8qm: add scu power key support
commit: f9c8aaffc782cae682d3606037f2d02fb4e0035a
Best regards,
--
Frank Li <Frank.Li@nxp.com>
prev parent reply other threads:[~2026-07-14 15:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-28 20:01 [PATCH 0/2] input: fsl,scu-key: Add compatible string fsl,imx8qm-sc-key Frank Li
2025-10-28 20:01 ` [PATCH 1/2] dt-bindings: " Frank Li
2025-10-29 6:54 ` Krzysztof Kozlowski
2026-01-05 20:03 ` Frank Li
2025-10-28 20:01 ` [PATCH 2/2] arm64: dts: imx8qm: add scu power key support Frank Li
2026-07-14 15:47 ` Frank.Li [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=178404388197.1628554.1376903172807695440.b4-ty@b4 \
--to=frank.li@oss.nxp.com \
--cc=Frank.Li@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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