From: Linus Walleij <linus.walleij@linaro.org>
To: Andrew Duggan <aduggan@synaptics.com>
Cc: Linux Input <linux-input@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Christopher Heiny <cheiny@synaptics.com>,
Stephen Chandler Paul <cpaul@redhat.com>,
Vincent Huang <vincent.huang@tw.synaptics.com>,
Chris Healy <cphealy@gmail.com>,
Andrey Gusakov <andrey.gusakov@cogentembedded.com>,
Rob Herring <robh@kernel.org>
Subject: Re: [PATCH v5 00/10] Input: synaptics-rmi4: Synaptics RMI4 Driver
Date: Fri, 12 Feb 2016 13:54:23 +0100 [thread overview]
Message-ID: <CACRpkdaE91ncWccG9_dsOiC40j9mFpm7A=S_mpeHmP-vjSVjMQ@mail.gmail.com> (raw)
In-Reply-To: <1455142982-10008-1-git-send-email-aduggan@synaptics.com>
On Wed, Feb 10, 2016 at 11:23 PM, Andrew Duggan <aduggan@synaptics.com> wrote:
> This is the v5 patch series which fixes the issues identified by kbuild
> and coccinelle in the previous patch series. These include:
>
> - Using ARRAY_SIZE instead of a custom macro to calculate the size of the
> function handler array.
> - Remove setting the .owner field for the driver in rmi_i2c and rmi_spi
> since the i2c-core and spi set that field.
> - Fix if statment in rmi_f30 which was testing has_led twice instead of
> testing has_gpio.
Works like a charm.
Tested-by: Linus Walleij <linus.walleij@linaro.org>
Yours,
Linus Walleij
next prev parent reply other threads:[~2016-02-12 12:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 22:23 [PATCH v5 00/10] Input: synaptics-rmi4: Synaptics RMI4 Driver Andrew Duggan
2016-02-11 10:05 ` Benjamin Tissoires
2016-02-11 21:37 ` Andrew Duggan
2016-02-12 7:56 ` Benjamin Tissoires
2016-02-12 12:54 ` Linus Walleij [this message]
2016-02-12 18:10 ` Andrew Duggan
2016-03-03 17:11 ` Benjamin Tissoires
2016-03-11 18:05 ` Dmitry Torokhov
2016-03-11 18:36 ` Andrew Duggan
2016-03-16 11:53 ` Linus Walleij
2016-02-15 22:48 ` Bjorn Andersson
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='CACRpkdaE91ncWccG9_dsOiC40j9mFpm7A=S_mpeHmP-vjSVjMQ@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=aduggan@synaptics.com \
--cc=andrey.gusakov@cogentembedded.com \
--cc=benjamin.tissoires@redhat.com \
--cc=cheiny@synaptics.com \
--cc=cpaul@redhat.com \
--cc=cphealy@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=vincent.huang@tw.synaptics.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).