From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Andrew Duggan <aduggan@synaptics.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH] Input: synaptics-rmi4: Remove check of Non-NULL array
Date: Thu, 17 Mar 2016 17:10:59 -0700 [thread overview]
Message-ID: <20160318001059.GC21461@dtor-ws> (raw)
In-Reply-To: <1458002101-4681-1-git-send-email-aduggan@synaptics.com>
On Mon, Mar 14, 2016 at 05:35:01PM -0700, Andrew Duggan wrote:
> Originally the irq_mask member of rmi_function was a pointer. Then it was
> switched to being a zero length array. However, the checks for a NULL
> pointer where not removed.
>
> Signed-off-by: Andrew Duggan <aduggan@synaptics.com>
Applied, thank you.
> ---
> drivers/input/rmi4/rmi_driver.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/input/rmi4/rmi_driver.c b/drivers/input/rmi4/rmi_driver.c
> index da38f0a..faa295e 100644
> --- a/drivers/input/rmi4/rmi_driver.c
> +++ b/drivers/input/rmi4/rmi_driver.c
> @@ -126,7 +126,7 @@ static void process_one_interrupt(struct rmi_driver_data *data,
> return;
>
> fh = to_rmi_function_handler(fn->dev.driver);
> - if (fn->irq_mask && fh->attention) {
> + if (fh->attention) {
> bitmap_and(data->fn_irq_bits, data->irq_status, fn->irq_mask,
> data->irq_count);
> if (!bitmap_empty(data->fn_irq_bits, data->irq_count))
> @@ -172,8 +172,7 @@ int rmi_process_interrupt_requests(struct rmi_device *rmi_dev)
> * use irq_chip.
> */
> list_for_each_entry(entry, &data->function_list, node)
> - if (entry->irq_mask)
> - process_one_interrupt(data, entry);
> + process_one_interrupt(data, entry);
>
> if (data->input)
> input_sync(data->input);
> --
> 2.5.0
>
--
Dmitry
prev parent reply other threads:[~2016-03-18 0:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 0:35 [PATCH] Input: synaptics-rmi4: Remove check of Non-NULL array Andrew Duggan
2016-03-18 0:10 ` 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=20160318001059.GC21461@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=aduggan@synaptics.com \
--cc=dan.carpenter@oracle.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).