From: Rob Herring <robh@kernel.org>
To: wyibo6109@gmail.com
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-input@vger.kernel.org,
Krzysztof Kozlowski <krzk@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/2] dt-bindings: input: add OnePlus pogo-pin keyboard
Date: Fri, 16 Oct 2026 08:11:59 -0500 [thread overview]
Message-ID: <20261016131159.GG5059-robh@kernel.org> (raw)
In-Reply-To: <20261016123255.1019102-1-wyibo6109@gmail.com>
On Fri, Oct 16, 2026 at 07:32:46AM -0500, wyibo6109@gmail.com wrote:
> From: Yibo Wang <wyibo6109@gmail.com>
>
> Hi Rob,
>
> thanks for the review.
>
> On 15/10/2026 15:15, Rob Herring wrote:
> > Don't need '|'.
>
> Dropped.
>
> > Wrap lines at 80 char.
>
> Rewrapped, everything now stays within 75 columns.
>
> > As this goes under 'serial' nodes:
> >
> > serial {
>
> Restored.
>
> v5 follows as a reply to the v4 cover letter.
Please don't send new versions as replies.
Rob
next prev parent reply other threads:[~2026-10-16 13:12 UTC|newest]
Thread overview: 33+ 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-16 13:11 ` Rob Herring [this message]
2026-10-16 16:35 ` 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
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=20261016131159.GG5059-robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=krzk@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 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.