kernel-janitors.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [PATCH -next] Input: synaptics-rmi4 - fix the error return code in rmi_probe_interrupts()
Date: Mon, 11 Jun 2018 17:10:12 +0000	[thread overview]
Message-ID: <20180611171012.GA251078@dtor-ws> (raw)
In-Reply-To: <6cdcc804be73a5e3bb6e8d70ab86dc716c5cc720.camel@redhat.com>

On Thu, Jun 07, 2018 at 02:16:43PM -0700, Nick Desaulniers wrote:
> On Thu, Jun 7, 2018 at 2:15 PM, Nick Desaulniers
> <nick.desaulniers@gmail.com> wrote:
> > On Thu, Jun 7, 2018 at 9:22 AM, Lyude Paul <lyude@redhat.com> wrote:
> >> Reviewed-by: Lyude Paul <lyude@redhat.com>
> >>
> >> On Thu, 2018-06-07 at 01:48 +0000, Wei Yongjun wrote:
> >>> The error return code PTR_ERR(data->irqdomain) is always 0 since
> >>> data->irqdomain is equal to NULL in this error handling case.
> >>>
> >>> Fixes: 24d28e4f1271 ("Input: synaptics-rmi4 - convert irq distribution to
> >>> irq_domain")
> >>> Signed-off-by: Wei Yongjun <weiyongjun1@huawei.com>
> >>> ---
> >>>  drivers/input/rmi4/rmi_driver.c | 2 +-
> >>>  1 file changed, 1 insertion(+), 1 deletion(-)
> >>>
> >>> diff --git a/drivers/input/rmi4/rmi_driver.c
> >>> b/drivers/input/rmi4/rmi_driver.c
> >>> index 2fb0ae0..cb6d983 100644
> >>> --- a/drivers/input/rmi4/rmi_driver.c
> >>> +++ b/drivers/input/rmi4/rmi_driver.c
> >>> @@ -1043,7 +1043,7 @@ int rmi_probe_interrupts(struct rmi_driver_data *data)
> >>>                                                  data);
> >>>       if (!data->irqdomain) {
> >>>               dev_err(&rmi_dev->dev, "Failed to create IRQ domain\n");
> >>> -             return PTR_ERR(data->irqdomain);
> >>> +             return -ENOMEM;
> >>>       }
> >>>
> >>>       data->irq_count = irq_count;
> >>>
> >>> --
> >>> To unsubscribe from this list: send the line "unsubscribe linux-input" in
> >>> the body of a message to majordomo@vger.kernel.org
> >>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> >> --
> >> Cheers,
> >>         Lyude Paul
> >
> > Signed-off-by: Nick Desaulniers <ndesaulniers@google.com>
> 
> Sorry, that probably should have been a
> 
> Reviewed-by: Nick Desaulniers <ndesaulniers@google.com>
> 
> hopefully that doesn't mess up any maintainers' automated scripts.

Applied, thank you.

-- 
Dmitry

  parent reply	other threads:[~2018-06-11 17:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-07 16:22 [PATCH -next] Input: synaptics-rmi4 - fix the error return code in rmi_probe_interrupts() Lyude Paul
2018-06-07 21:15 ` Nick Desaulniers
2018-06-07 21:16 ` Nick Desaulniers
2018-06-11 17:10 ` Dmitry Torokhov [this message]
2020-04-28 13:49 ` [PATCH -next] Input: synaptics-rmi4 - fix error return code in rmi_driver_probe() Wei Yongjun
2020-04-28 23:10   ` Dmitry Torokhov
  -- strict thread matches above, loose matches on Subject: below --
2018-06-07  1:48 [PATCH -next] Input: synaptics-rmi4 - fix the error return code in rmi_probe_interrupts() Wei Yongjun

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=20180611171012.GA251078@dtor-ws \
    --to=dmitry.torokhov@gmail.com \
    --cc=kernel-janitors@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).