public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@infradead.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Giedrius Statkevicius <giedriuswork@gmail.com>,
	platform-driver-x86@vger.kernel.org,
	linux-kernel@vger.kernel.org, Alex Hung <alex.hung@canonical.com>
Subject: Re: [PATCH] platform: x86: hp_wireless: Inform the user if hp_wireless_input_setup()/add() fails
Date: Tue, 25 Nov 2014 14:57:19 -0800	[thread overview]
Message-ID: <20141125225719.GA32102@vmdeb7> (raw)
In-Reply-To: <20141129000417.GG30997@pd.tnic>

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@gmail.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

  reply	other threads:[~2014-12-02  7:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-28 22:14 [PATCH] platform: x86: hp_wireless: Inform the user if hp_wireless_input_setup()/add() fails Giedrius Statkevicius
2014-11-28 23:15 ` Borislav Petkov
2014-11-28 23:48   ` Giedrius Statkevicius
2014-11-29  0:04     ` Borislav Petkov
2014-11-25 22:57       ` Darren Hart [this message]
2014-12-02 16:15         ` Giedrius Statkevicius
2014-12-02 17:19           ` Darren Hart
2014-12-01  7:22       ` Alex Hung

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=20141125225719.GA32102@vmdeb7 \
    --to=dvhart@infradead.org \
    --cc=alex.hung@canonical.com \
    --cc=bp@alien8.de \
    --cc=giedriuswork@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@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