From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
Wolfram Sang <wsa@the-dreams.de>,
linux-input@vger.kernel.org, linux-i2c@vger.kernel.org,
devicetree@vger.kernel.org, linux-sh@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH v2 0/2] Fix OF match for adxl34x driver
Date: Thu, 21 May 2015 13:42:24 +0200 [thread overview]
Message-ID: <1432208546-18615-1-git-send-email-geert+renesas@glider.be> (raw)
Hi Dmitry,
This is a resent of a series by Laurent Pinchart to fix OF matching for
the adxl34x driver.
According to the discussion in response to that series, we were under
the impression this was going in through the input tree
(http://www.spinics.net/lists/linux-i2c/msg18293.html).
In input patchwork, the series is still marked "Awaiting Upstream"
(https://patchwork.ozlabs.org/project/linux-i2c/list/?state=*&q=adxl),
but actually we are waiting for you, as we can't update the affected DTS
before the driver fix has gone in ;-)
>From Laurent's submission:
This patch set fixes OF matching for the adxl34x driver when the DT
node lists a device-specific "adi,adxl345" or "adi,adxl346"
compatible value first.
The first version (see
http://www.spinics.net/lists/linux-i2c/msg18107.html) added an OF
match entry for the "adi,adxl34x" compatible string. The discussion
that followed concluded that that compatible string should be
deprecated and that the driver should match the device-specific
strings instead.
The first patch thus deprecates the "adi,adxl34x" compatible string
by removing it the DT trivial devices list, and the second patch
then adds an OF match table to the adxl34x driver.
Thanks for applying!
Laurent Pinchart (2):
DT: i2c: Deprecate adi,adxl34x compatible string
input: adxl34x: Add OF match support
.../devicetree/bindings/i2c/trivial-devices.txt | 3 +--
drivers/input/misc/adxl34x-i2c.c | 21 +++++++++++++++++++++
2 files changed, 22 insertions(+), 2 deletions(-)
--
1.9.1
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next reply other threads:[~2015-05-21 11:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 11:42 Geert Uytterhoeven [this message]
2015-05-21 11:42 ` [PATCH v2 1/2] DT: i2c: Deprecate adi,adxl34x compatible string Geert Uytterhoeven
2015-05-22 1:32 ` Simon Horman
[not found] ` <1432208546-18615-1-git-send-email-geert+renesas-gXvu3+zWzMSzQB+pC5nmwQ@public.gmane.org>
2015-05-21 11:42 ` [PATCH v2 2/2] input: adxl34x: Add OF match support Geert Uytterhoeven
[not found] ` <1432208546-18615-3-git-send-email-geert+renesas-gXvu3+zWzMSzQB+pC5nmwQ@public.gmane.org>
2015-05-22 1:32 ` Simon Horman
2015-05-22 23:32 ` [PATCH v2 0/2] Fix OF match for adxl34x driver Dmitry Torokhov
2015-05-23 7:10 ` Geert Uytterhoeven
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=1432208546-18615-1-git-send-email-geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=wsa@the-dreams.de \
/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).