From: Darren Hart <dvhart@infradead.org>
To: Alex Hung <alex.hung@canonical.com>
Cc: andy@infradead.org, platform-driver-x86@vger.kernel.org,
rjw@rjwysocki.net
Subject: Re: [PATCH] platform/x86: intel-vbtn: reduce unnecessary messages for normal users
Date: Fri, 21 Jul 2017 16:16:20 -0700 [thread overview]
Message-ID: <20170721231620.GB7888@fury> (raw)
In-Reply-To: <1500609408-30745-1-git-send-email-alex.hung@canonical.com>
On Thu, Jul 20, 2017 at 08:56:48PM -0700, Alex Hung wrote:
> Unsupported events is only useful for developers and does not meaningful
> for users. Using dev_dbg makes more sense and reduces noise in kernel
> messages.
>
> Signed-off-by: Alex Hung <alex.hung@canonical.com>
> ---
> drivers/platform/x86/intel-vbtn.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/platform/x86/intel-vbtn.c b/drivers/platform/x86/intel-vbtn.c
> index 61f1063..10f92ac 100644
> --- a/drivers/platform/x86/intel-vbtn.c
> +++ b/drivers/platform/x86/intel-vbtn.c
> @@ -83,7 +83,7 @@ static void notify_handler(acpi_handle handle, u32 event, void *context)
> } else if (sparse_keymap_report_event(priv->input_dev, event, 1, true)) {
> return;
> }
> - dev_info(&device->dev, "unknown event index 0x%x\n", event);
> + dev_dbg(&device->dev, "unknown event index 0x%x\n", event);
info is the most common log level for these events in the platform
driver x86 subsystem per 'git grep -i "unknown event"'.
My take on this is that we want these to be reported by users, rather
than rely on developers to find them all - especially as the developers
only see a fraction of the affected hardware.
Are you finding these to be causing a problem / or producing really
excessive log messages?
Andy, what are your thoughts?
> }
>
> static int intel_vbtn_probe(struct platform_device *device)
> --
> 2.7.4
>
>
--
Darren Hart
VMware Open Source Technology Center
next prev parent reply other threads:[~2017-07-21 23:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-21 3:56 [PATCH] platform/x86: intel-vbtn: reduce unnecessary messages for normal users Alex Hung
2017-07-21 23:16 ` Darren Hart [this message]
2017-07-22 21:51 ` Rafael J. Wysocki
2017-07-24 9:19 ` Andy Shevchenko
2017-07-24 11:41 ` Rafael J. Wysocki
2017-07-25 1:14 ` Darren Hart
2017-07-25 15:30 ` Darren Hart
2017-07-28 1:01 ` Rafael J. Wysocki
2017-07-28 18:52 ` Darren Hart
2017-08-18 23:25 ` 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=20170721231620.GB7888@fury \
--to=dvhart@infradead.org \
--cc=alex.hung@canonical.com \
--cc=andy@infradead.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.