From: Hans de Goede <hdegoede@redhat.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>, linux-input@vger.kernel.org
Cc: Yunkang Tang <yunkang.tang@cn.alps.com>,
Paul Menzel <paulepanter@users.sourceforge.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: ALPS - suppress message about 'Unknown touchpad'
Date: Tue, 26 Aug 2014 10:20:54 +0200 [thread overview]
Message-ID: <53FC4366.7050600@redhat.com> (raw)
In-Reply-To: <20140825183031.GA5151@core.coreip.homeip.net>
Hi,
On 08/25/2014 08:30 PM, Dmitry Torokhov wrote:
> When we fail to match data returned by E7 and EC reports we state that we
> found "Unknown ALPS touchpad" whereas it is most likely it is not ALPS
> touchpad at all. Change wording a bit and reduce the message to debug so
> that it does not litter users logs and confuse them.
>
> Reported-by: Paul Menzel <paulepanter@users.sourceforge.net>
> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
I noticed this too, and I agree that it is a confusing message:
Acked-by: Hans de Goede <hdegoede@redhat.com>
Regards,
Hans
> ---
> drivers/input/mouse/alps.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/input/mouse/alps.c b/drivers/input/mouse/alps.c
> index a59a1a6..a956b98 100644
> --- a/drivers/input/mouse/alps.c
> +++ b/drivers/input/mouse/alps.c
> @@ -2234,8 +2234,8 @@ static int alps_identify(struct psmouse *psmouse, struct alps_data *priv)
> return 0;
> }
>
> - psmouse_info(psmouse,
> - "Unknown ALPS touchpad: E7=%3ph, EC=%3ph\n", e7, ec);
> + psmouse_dbg(psmouse,
> + "Likely not an ALPS touchpad: E7=%3ph, EC=%3ph\n", e7, ec);
>
> return -EINVAL;
> }
>
prev parent reply other threads:[~2014-08-26 8:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-25 18:30 [PATCH] Input: ALPS - suppress message about 'Unknown touchpad' Dmitry Torokhov
2014-08-26 8:20 ` Hans de Goede [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=53FC4366.7050600@redhat.com \
--to=hdegoede@redhat.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulepanter@users.sourceforge.net \
--cc=yunkang.tang@cn.alps.com \
/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).