From: Jeremiah Mahler <jmmahler@gmail.com>
To: Dudley Du <dudl@cypress.com>
Cc: dmitry.torokhov@gmail.com, linux-kernel@vger.kernel.org
Subject: input: cyapa: failed to read report data, (-121)
Date: Fri, 15 Jan 2016 11:43:55 -0800 [thread overview]
Message-ID: <20160115194355.GA4086@hudson.localdomain> (raw)
Dudley,
On my Acer C720 I have noticed the following messages in the
logs related to cyapa.
...
[ 830.406225] wlan0: RX AssocResp from ec:1a:59:f5:fa:80 (capab=0x411 status=0 aid=2)
[ 830.406309] wlan0: associated
[ 1004.312209] cyapa 0-0067: failed to read report data, (-121)
[ 2432.690556] cyapa 0-0067: failed to read report data, (-121)
[ 3725.946455] cyapa 0-0067: failed to read report data, (-121)
They were present before your recent patch [1], and they are still present
after, so it has nothing to do with that. And everything appears to
work fine. I just thought I would let you know in case it is something
might be concerned about.
[1]: http://marc.info/?l=linux-kernel&m=145275125112675&w=2
--
- Jeremiah Mahler
reply other threads:[~2016-01-15 19:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20160115194355.GA4086@hudson.localdomain \
--to=jmmahler@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=dudl@cypress.com \
--cc=linux-kernel@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