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-hid: reduce unnecessary messages for normal users
Date: Fri, 21 Jul 2017 16:17:03 -0700 [thread overview]
Message-ID: <20170721231703.GC7888@fury> (raw)
In-Reply-To: <1500609488-30813-1-git-send-email-alex.hung@canonical.com>
On Thu, Jul 20, 2017 at 08:58:08PM -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.
Similar thoughts here as to intel-vbtn. Let's discuss on that thread and apply
the same decision here.
>
> Signed-off-by: Alex Hung <alex.hung@canonical.com>
> ---
> drivers/platform/x86/intel-hid.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/platform/x86/intel-hid.c b/drivers/platform/x86/intel-hid.c
> index 8519e0f..4f70b82 100644
> --- a/drivers/platform/x86/intel-hid.c
> +++ b/drivers/platform/x86/intel-hid.c
> @@ -219,7 +219,7 @@ static void notify_handler(acpi_handle handle, u32 event, void *context)
> if (event != 0xc0) {
> if (!priv->array ||
> !sparse_keymap_report_event(priv->array, event, 1, true))
> - dev_info(&device->dev, "unknown event 0x%x\n", event);
> + dev_dbg(&device->dev, "unknown event 0x%x\n", event);
> return;
> }
>
> @@ -230,7 +230,7 @@ static void notify_handler(acpi_handle handle, u32 event, void *context)
> }
>
> if (!sparse_keymap_report_event(priv->input_dev, ev_index, 1, true))
> - dev_info(&device->dev, "unknown event index 0x%llx\n",
> + dev_dbg(&device->dev, "unknown event index 0x%llx\n",
> ev_index);
> }
>
> --
> 2.7.4
>
>
--
Darren Hart
VMware Open Source Technology Center
prev parent reply other threads:[~2017-07-21 23:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-21 3:58 [PATCH] platform/x86: intel-hid: reduce unnecessary messages for normal users Alex Hung
2017-07-21 23:17 ` Darren Hart [this message]
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=20170721231703.GC7888@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox