All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff LaBundy <jeff@labundy.com>
To: dmitry.torokhov@gmail.com, robh+dt@kernel.org
Cc: linux-input@vger.kernel.org, devicetree@vger.kernel.org,
	jeff@labundy.com
Subject: [PATCH v2 0/2] Miscellaneous fixes for Azoteq IQS626A
Date: Fri, 27 Jan 2023 16:28:25 -0600	[thread overview]
Message-ID: <Y9RQCQa69f3TaiWf@nixie71> (raw)

This series addresses a fwnode_handle reference count leak. Tightly
coupled with this logic is that behind the discussion in [1], where
it was pointed out that two properties in question have different
types across bindings for the same vendor.

Addressing the latter in fact simplifies the former; therefore both
changes are introduced in patch [1/2]. As there are no known users
of this driver, it is safe to change the binding in this way.

Patch [2/2] makes the corresponding documentation change and carries
a fixes tag so that it accompanies patch [1/2] into stable releases.

[1] https://patchwork.kernel.org/patch/13116327/

Jeff LaBundy (2):
  Input: iqs626a - drop unused device node references
  dt-bindings: input: iqs626a: Redefine trackpad property types

 .../devicetree/bindings/input/iqs626a.yaml    |  94 ++++++++---
 drivers/input/misc/iqs626a.c                  | 156 ++++++++----------
 2 files changed, 140 insertions(+), 110 deletions(-)

-- 
2.34.1


             reply	other threads:[~2023-01-27 22:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-27 22:28 Jeff LaBundy [this message]
2023-01-27 22:29 ` [PATCH v2 1/2] Input: iqs626a - drop unused device node references Jeff LaBundy
2023-02-04  1:21   ` Dmitry Torokhov
2023-01-27 22:30 ` [PATCH v2 2/2] dt-bindings: input: iqs626a: Redefine trackpad property types Jeff LaBundy
2023-01-30 21:23   ` Rob Herring
2023-02-04  1:22   ` Dmitry Torokhov

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=Y9RQCQa69f3TaiWf@nixie71 \
    --to=jeff@labundy.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=robh+dt@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 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.