From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Vincent Knecht <vincent.knecht@mailoo.org>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
w.david0@protonmail.com, stephan@gerhold.net,
phone-devel@vger.kernel.org
Subject: Re: [PATCH RESEND] Input: msg2638 - only read linux,keycodes array if necessary
Date: Wed, 30 Nov 2022 15:15:56 -0800 [thread overview]
Message-ID: <Y4fkLL6nvq6655MW@google.com> (raw)
In-Reply-To: <20221130210202.2069213-1-vincent.knecht@mailoo.org>
On Wed, Nov 30, 2022 at 10:01:59PM +0100, Vincent Knecht wrote:
> The linux,keycodes property is optional.
> Fix the driver not probing when it's not specified.
>
> Fixes: c18ef50346f2 ("Input: msg2638 - add support for msg2138 key events")
> Signed-off-by: Vincent Knecht <vincent.knecht@mailoo.org>
Applied, thank you.
--
Dmitry
prev parent reply other threads:[~2022-11-30 23:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 21:01 [PATCH RESEND] Input: msg2638 - only read linux,keycodes array if necessary Vincent Knecht
2022-11-30 23:15 ` Dmitry Torokhov [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=Y4fkLL6nvq6655MW@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phone-devel@vger.kernel.org \
--cc=stephan@gerhold.net \
--cc=vincent.knecht@mailoo.org \
--cc=w.david0@protonmail.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;
as well as URLs for NNTP newsgroup(s).