From: Krzysztof Kozlowski <krzk@kernel.org>
To: Manuel Ebner <manuelebner@mailbox.org>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh@kernel.org>
Cc: devicetree@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH] dt-bindings: fix typos and brackets
Date: Sat, 11 Jul 2026 15:27:19 +0200 [thread overview]
Message-ID: <78b49c32-1ec4-4b5a-bebd-feb9531bcf70@kernel.org> (raw)
In-Reply-To: <3f51a907c0a5e9c44d169d67d43ebff36f8f42c8.camel@mailbox.org>
On 11/07/2026 15:18, Manuel Ebner wrote:
> - The charlieplex keypad supports N^2)-N different key combinations (where N is
> + The charlieplex keypad supports (N^2)-N different key combinations (where N is
> the number of I/O lines). Key presses and releases are detected by configuring
> only one line as output at a time, and reading other line states. This process
> is repeated for each line. Diodes are required to ensure current flows in only
> diff --git a/Documentation/devicetree/bindings/leds/backlight/88pm860x.txt
> b/Documentation/devicetree/bindings/leds/backlight/88pm860x.txt
> index 261df2799315..9e17807d2ce5 100644
> --- a/Documentation/devicetree/bindings/leds/backlight/88pm860x.txt
> +++ b/Documentation/devicetree/bindings/leds/backlight/88pm860x.txt
> @@ -13,3 +13,4 @@ Example:
> };
> backlight-2 {
> };
> + };
There is no such context in that file. Your patch looks corrupted.
Best regards,
Krzysztof
prev parent reply other threads:[~2026-07-11 13:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-11 13:18 [PATCH] dt-bindings: fix typos and brackets Manuel Ebner
2026-07-11 13:27 ` Krzysztof Kozlowski [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=78b49c32-1ec4-4b5a-bebd-feb9531bcf70@kernel.org \
--to=krzk@kernel.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manuelebner@mailbox.org \
--cc=rdunlap@infradead.org \
--cc=robh@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