From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Jeff LaBundy <jeff@labundy.com>
Cc: linux-input@vger.kernel.org
Subject: Re: [PATCH v2] Input: iqs7211 - point to match data directly
Date: Thu, 13 Jul 2023 12:02:25 -0700 [thread overview]
Message-ID: <ZLBKQadqBgEqInzq@google.com> (raw)
In-Reply-To: <ZLA+cuciIeVcCvm6@nixie71>
On Thu, Jul 13, 2023 at 01:12:02PM -0500, Jeff LaBundy wrote:
> Point the OF match table directly to the struct that describes the
> device as opposed to an intermediate enum; doing so simplifies the
> code and avoids a clang warning.
>
> As part of this change, the I2C device ID table is removed, as the
> device cannot probe without an OF node due to the unique nature of
> the hardware's interrupt pin.
>
> Fixes: f2ba47e65f3b ("Input: add support for Azoteq IQS7210A/7211A/E")
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202307131717.LtwApG0z-lkp@intel.com/
> Signed-off-by: Jeff LaBundy <jeff@labundy.com>
Applied, thank you.
--
Dmitry
prev parent reply other threads:[~2023-07-13 19:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 18:12 [PATCH v2] Input: iqs7211 - point to match data directly Jeff LaBundy
2023-07-13 19:02 ` 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=ZLBKQadqBgEqInzq@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=jeff@labundy.com \
--cc=linux-input@vger.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