From: Jonathan Woithe <jwoithe@just42.net>
To: Micha?? K??pie?? <kernel@kempniu.pl>
Cc: Darren Hart <dvhart@infradead.org>,
Andy Shevchenko <andy@infradead.org>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] platform/x86: fujitsu-laptop: update debug message logged by call_fext_func()
Date: Fri, 7 Apr 2017 21:10:19 +0930 [thread overview]
Message-ID: <20170407114019.GA15240@marvin.atrad.com.au> (raw)
In-Reply-To: <20170406064610.13984-1-kernel@kempniu.pl>
On Thu, Apr 06, 2017 at 08:46:10AM +0200, Micha?? K??pie?? wrote:
> Update debug message logged when the acpi_evaluate_integer() call inside
> call_fext_func() fails so that it covers a broader set of possible
> errors.
>
> Signed-off-by: Micha?? K??pie?? <kernel@kempniu.pl>
> ---
> This patch is a follow-up to v1 of the call_fext_func() cleanup series
> and as such, it should be applied to for-next.
>
> drivers/platform/x86/fujitsu-laptop.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/platform/x86/fujitsu-laptop.c b/drivers/platform/x86/fujitsu-laptop.c
> index 26149f58dba7..928778ccc4c1 100644
> --- a/drivers/platform/x86/fujitsu-laptop.c
> +++ b/drivers/platform/x86/fujitsu-laptop.c
> @@ -232,7 +232,7 @@ static int call_fext_func(int func, int op, int feature, int state)
> status = acpi_evaluate_integer(fujitsu_laptop->acpi_handle, "FUNC",
> &arg_list, &value);
> if (ACPI_FAILURE(status)) {
> - vdbg_printk(FUJLAPTOP_DBG_ERROR, "FUNC interface is not present\n");
> + vdbg_printk(FUJLAPTOP_DBG_ERROR, "Failed to evaluate FUNC\n");
> return -ENODEV;
> }
As per discussions on the list, this change is fine, is consistent with the
generic nature of possible failure modes and makes sense in the context of
the other recent changes.
Reviewed-by: Jonathan Woithe <jwoithe@just42.net>
Regards
jonathan
next prev parent reply other threads:[~2017-04-07 11:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-06 6:46 Michał Kępień
2017-04-07 11:40 ` Jonathan Woithe [this message]
2017-04-07 17:51 ` Darren Hart
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=20170407114019.GA15240@marvin.atrad.com.au \
--to=jwoithe@just42.net \
--cc=andy@infradead.org \
--cc=dvhart@infradead.org \
--cc=kernel@kempniu.pl \
--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
Powered by JetHome