From: sashiko-bot@kernel.org
To: wyibo6109@gmail.com, linux-input@vger.kernel.org
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org,
dmitry.torokhov@gmail.com
Subject: Re: [PATCH v5 1/2] dt-bindings: input: add OnePlus pogo-pin keyboard
Date: Fri, 16 Oct 2026 12:38:52 +0000 [thread overview]
Message-ID: <sashiko-outbox-174304@kernel.org> (raw)
In-Reply-To: <20261016123334.1019257-2-wyibo6109@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] MAINTAINERS: alphabetical sorting error for ONEPLUS entry
--
commit d93ea6ab73044ac76b5e3e2c76b82b975bf6fd6f
Author: Yibo Wang <wyibo6109@gmail.com>
dt-bindings: input: add OnePlus pogo-pin keyboard
This patch adds the device tree binding for the OnePlus Pad 3 Pro / Pad 4
and OPPO Pad 5 Pro pogo-pin smart keyboards. It defines the compatible
strings, required GPIO properties, and adds a MAINTAINERS entry.
> diff --git a/MAINTAINERS b/MAINTAINERS
> index b8c4e1080af94..d81e400059ced 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
[ ... ]
> @@ -20154,6 +20154,12 @@ S: Maintained
> F: Documentation/ABI/testing/sysfs-bus-platform-onboard-usb-dev
> F: drivers/usb/misc/onboard_usb_dev.c
>
> +ONEPLUS POGO-PIN KEYBOARD DRIVER
> +M: Yibo Wang <wyibo6109@gmail.com>
> +L: linux-input@vger.kernel.org
> +S: Maintained
> +F: Documentation/devicetree/bindings/input/oneplus,pogo-keyboard.yaml
> +
> ONENAND FLASH DRIVER
[Severity: Low]
This isn't a bug, but should the ONEPLUS entry be placed after the ONENAND
entry? The MAINTAINERS file is expected to be kept in strict alphabetical
order, and ONEP... follows ONEN... alphabetically.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261016123334.1019257-1-wyibo6109@gmail.com?part=1
next prev parent reply other threads:[~2026-10-16 12:38 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 12:20 [PATCH 0/2] Input: add support for OnePlus/OPPO Pad pogo-pin keyboards wyibo6109
2026-10-09 12:20 ` [PATCH 1/2] dt-bindings: input: add OnePlus pogo-pin keyboard binding wyibo6109
2026-10-09 12:28 ` sashiko-bot
2026-10-09 13:22 ` Krzysztof Kozlowski
2026-10-09 12:20 ` [PATCH 2/2] Input: add OnePlus/OPPO Pad pogo-pin keyboard serdev driver wyibo6109
2026-10-09 12:38 ` sashiko-bot
2026-10-10 14:38 ` [PATCH v2 0/2] Input: add support for OnePlus/OPPO Pad pogo-pin keyboards wyibo6109
2026-10-10 14:38 ` [PATCH v2 1/2] dt-bindings: input: add OnePlus pogo-pin keyboard wyibo6109
2026-10-10 14:47 ` sashiko-bot
2026-10-12 6:24 ` Krzysztof Kozlowski
2026-10-14 13:47 ` wyibo6109
2026-10-15 8:52 ` Krzysztof Kozlowski
2026-10-15 11:08 ` wyibo6109
2026-10-10 14:38 ` [PATCH v2 2/2] Input: add OnePlus/OPPO Pad pogo-pin keyboard serdev driver wyibo6109
2026-10-10 14:48 ` sashiko-bot
2026-10-14 13:52 ` [PATCH v3 0/2] Input: add support for OnePlus/OPPO Pad pogo-pin keyboards wyibo6109
2026-10-14 13:52 ` [PATCH v3 1/2] dt-bindings: input: add OnePlus pogo-pin keyboard wyibo6109
2026-10-15 8:50 ` Krzysztof Kozlowski
2026-10-14 13:52 ` [PATCH v3 2/2] Input: add OnePlus/OPPO Pad pogo-pin keyboard serdev driver wyibo6109
2026-10-14 14:03 ` sashiko-bot
2026-10-15 11:08 ` [PATCH v4 0/2] Input: add support for OnePlus/OPPO Pad pogo-pin keyboards wyibo6109
2026-10-15 11:08 ` [PATCH v4 1/2] dt-bindings: input: add OnePlus pogo-pin keyboard wyibo6109
2026-10-15 20:15 ` Rob Herring
2026-10-16 12:32 ` wyibo6109
2026-10-15 11:08 ` [PATCH v4 2/2] Input: add OnePlus/OPPO Pad pogo-pin keyboard serdev driver wyibo6109
2026-10-15 11:19 ` sashiko-bot
2026-10-16 12:33 ` [PATCH v5 0/2] Input: add support for OnePlus/OPPO Pad pogo-pin keyboards wyibo6109
2026-10-16 12:33 ` [PATCH v5 1/2] dt-bindings: input: add OnePlus pogo-pin keyboard wyibo6109
2026-10-16 12:38 ` sashiko-bot [this message]
2026-10-16 12:33 ` [PATCH v5 2/2] Input: add OnePlus/OPPO Pad pogo-pin keyboard serdev driver wyibo6109
2026-10-16 12:48 ` sashiko-bot
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=sashiko-outbox-174304@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=wyibo6109@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox