From: Lee Jones <lee@kernel.org>
To: "Colin King (gmail)" <colin.i.king@gmail.com>
Cc: "Nuno Sá" <nuno.sa@analog.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: mfd: adp5585: add support for key events
Date: Thu, 1 May 2025 12:19:52 +0100 [thread overview]
Message-ID: <20250501111952.GG1567507@google.com> (raw)
In-Reply-To: <7a6d0a8a-aa14-488e-9072-0bbafaa84e5e@gmail.com>
On Thu, 01 May 2025, Colin King (gmail) wrote:
> Hi,
>
> I noticed that there is an issue with the naming of device tree property in
> the commit:
>
> commit f674cea99d03199a4fc9a96c68149b8804053f80
> Author: Nuno Sá <nuno.sa@analog.com>
> Date: Tue Apr 15 15:49:26 2025 +0100
>
> mfd: adp5585: add support for key events
>
>
> There is a property named "rst-passtrough-enable", should that be in fact
> "rst-passthrough-enable"? (an h is missing)
Why not send a patch like you usually do?
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2025-05-01 11:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-01 11:09 Colin King (gmail)
2025-05-01 11:19 ` Lee Jones [this message]
2025-05-02 7:37 ` Nuno Sá
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=20250501111952.GG1567507@google.com \
--to=lee@kernel.org \
--cc=colin.i.king@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.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
all inboxes | Powered by JetHome®