From: Ryan Brue <ryanbrue.dev@gmail.com>
To: sashiko-reviews@lists.linux.dev
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH 3/5] arm64: dts: mediatek: mt8173: Add the keypad controller
Date: Wed, 11 Nov 2026 13:37:06 -0600 [thread overview]
Message-ID: <b005af5b-96a3-47da-b53d-5dd034b6d56b@gmail.com> (raw)
In-Reply-To: <sashiko-outbox-209542@kernel.org>
On 11/11/26 1:14 PM, sashiko-bot@kernel.org wrote:
> [Severity: Low]
> Should "mediatek,mt8173-keypad" be documented in
> Documentation/devicetree/bindings/input/mediatek,mt6779-keypad.yaml first?
> Without adding it to the compatible enum in the binding schema, this causes
> checkpatch.pl warnings and dtbs_check validation failures on MT8173 device
> trees.
The compatible is documented in [1], which is queued in input already. I
couldn't make this series depend on it because the keypad binding as
posted didn't apply cleanly to v7.4-rc2. Hopefully this is not a problem.
[1]
https://lore.kernel.org/all/20260915-rbrue-suez-upstreaming-mt8173-keypad-v1-1-96c325efacbe@gmail.com/
Best Regards,
Ryan Brue
next prev parent reply other threads:[~2026-11-11 19:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 18:19 [PATCH 0/5] arm64: dts: mediatek: Add the Amazon Fire HD 10 (2017) Ryan Brue
2026-11-11 18:19 ` [PATCH 1/5] dt-bindings: arm: mediatek: Add MT8173 Amazon suez Ryan Brue
2026-11-11 18:19 ` [PATCH 2/5] arm64: dts: " Ryan Brue
2026-11-11 18:19 ` [PATCH 3/5] arm64: dts: mediatek: mt8173: Add the keypad controller Ryan Brue
2026-11-11 19:14 ` sashiko-bot
2026-11-11 19:37 ` Ryan Brue [this message]
2026-11-11 18:19 ` [PATCH 4/5] arm64: dts: mediatek: mt8173-amazon-suez: Enable the volume keys Ryan Brue
2026-11-11 19:31 ` sashiko-bot
2026-11-11 19:38 ` Ryan Brue
2026-11-11 18:19 ` [PATCH 5/5] arm64: dts: mediatek: mt8173-amazon-suez: Add the PMIC AUXADC Ryan Brue
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=b005af5b-96a3-47da-b53d-5dd034b6d56b@gmail.com \
--to=ryanbrue.dev@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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.