[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141125225719.GA32102@vmdeb7>
Date: Tue, 25 Nov 2014 14:57:19 -0800
From: Darren Hart <dvhart@...radead.org>
To: Borislav Petkov <bp@...en8.de>
Cc: Giedrius Statkevicius <giedriuswork@...il.com>,
platform-driver-x86@...r.kernel.org, linux-kernel@...r.kernel.org,
Alex Hung <alex.hung@...onical.com>
Subject: Re: [PATCH] platform: x86: hp_wireless: Inform the user if
hp_wireless_input_setup()/add() fails
On Sat, Nov 29, 2014 at 01:04:17AM +0100, Borislav Petkov wrote:
> On Sat, Nov 29, 2014 at 01:48:31AM +0200, Giedrius Statkevicius wrote:
> > On 2014.11.29 01:15, Borislav Petkov wrote:
> > > On Sat, Nov 29, 2014 at 12:14:27AM +0200, Giedrius Statkevicius wrote:
> > >> In hpwl_add() there is a unused variable err to which we assign the
> > >> result of hp_wireless_input_setup() but we don't do anything depending
> > >> on the result so print out a message that informs the user if add()
> > >> (hp_wireless_input_setup()) fails since acpi_device_probe() doesn't
> > >> print anything in this case.
> > >>
> > >> Signed-off-by: Giedrius Statkevicius <giedriuswork@...il.com>
> > >> ---
> > >> drivers/platform/x86/hp-wireless.c | 3 +++
> > >> 1 file changed, 3 insertions(+)
> > >>
> > >> diff --git a/drivers/platform/x86/hp-wireless.c b/drivers/platform/x86/hp-wireless.c
> > >> index 415348f..4e4cc8b 100644
> > >> --- a/drivers/platform/x86/hp-wireless.c
> > >> +++ b/drivers/platform/x86/hp-wireless.c
> > >> @@ -85,6 +85,9 @@ static int hpwl_add(struct acpi_device *device)
> > >> int err;
> > >>
> > >> err = hp_wireless_input_setup();
> > >> + if (err)
> > >> + pr_err("Failed to setup hp wireless hotkeys\n");
> > >> +
> > >
> > > I don't think there's need for that. Just do:
> > >
> > > return hp_wireless_input_setup();
> > >
> > > and drop err completely.
> > >
> > > The upper layer which calls the ->add() method should propagate the
> > > error properly.
This is the key. If the caller already prints a message, we don't need to. If
nothing is displayed and the user would be left confused, then an appropriate
message should be displayed.
If the upper level already handles this, then we can just drop the unused
variable.
Have a look and decide which is the most appropriate. And thanks for preparing a
fix.
--
Darren Hart
Intel Open Source Technology Center
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists