linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Kosina <jikos@kernel.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Benjamin Tissoires <benjamin.tissoires@redhat.com>,
	linux-input@vger.kernel.org
Subject: Re: [PATCH] HID: core: lower log level for unknown main item tags to warnings
Date: Thu, 7 Dec 2017 11:06:29 +0100 (CET)	[thread overview]
Message-ID: <nycvar.YFH.7.76.1712071106200.3572@cbobk.fhfr.pm> (raw)
In-Reply-To: <20171206165438.676-1-hdegoede@redhat.com>

On Wed, 6 Dec 2017, Hans de Goede wrote:

> Given all the effort distros have done with splash-screens to give
> users a nice clean boot experience, we really want dmesg --level=err
> to not print anything unless there is a real problem with either the
> hardware or the kernel. Buggy HID descriptors unfortunately happen
> all too often, so lower the log level to warning keep the console
> clear of error messages such as:
> 
> [  441.079664] apple 0005:05AC:0239.0003: unknown main item tag 0x0
> 
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
> ---
>  drivers/hid/hid-core.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/hid/hid-core.c b/drivers/hid/hid-core.c
> index 7297b1d1300c..c2560aae5542 100644
> --- a/drivers/hid/hid-core.c
> +++ b/drivers/hid/hid-core.c
> @@ -551,7 +551,7 @@ static int hid_parser_main(struct hid_parser *parser, struct hid_item *item)
>  		ret = hid_add_field(parser, HID_FEATURE_REPORT, data);
>  		break;
>  	default:
> -		hid_err(parser->device, "unknown main item tag 0x%x\n", item->tag);
> +		hid_warn(parser->device, "unknown main item tag 0x%x\n", item->tag);
>  		ret = 0;

Applied to for-4.15/upstream-fixes. Thanks,

-- 
Jiri Kosina
SUSE Labs


      parent reply	other threads:[~2017-12-07 10:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-06 16:54 [PATCH] HID: core: lower log level for unknown main item tags to warnings Hans de Goede
2017-12-06 17:24 ` Benjamin Tissoires
2017-12-07 10:06 ` Jiri Kosina [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=nycvar.YFH.7.76.1712071106200.3572@cbobk.fhfr.pm \
    --to=jikos@kernel.org \
    --cc=benjamin.tissoires@redhat.com \
    --cc=hdegoede@redhat.com \
    --cc=linux-input@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;
as well as URLs for NNTP newsgroup(s).