From: Kalle Valo <kvalo@codeaurora.org>
To: Brian Norris <briannorris@chromium.org>
Cc: Amitkumar Karwar <akarwar@marvell.com>,
Nishant Sarmukadam <nishants@marvell.com>,
<linux-kernel@vger.kernel.org>,
linux-wireless@vger.kernel.org, Cathy Luo <cluo@marvell.com>,
Brian Norris <briannorris@chromium.org>
Subject: Re: mwifiex: don't complain about 'unknown event id: 0x63'
Date: Fri, 20 Jan 2017 09:47:46 +0000 (UTC) [thread overview]
Message-ID: <20170120094746.8FDEC609C9@smtp.codeaurora.org> (raw)
In-Reply-To: <20170114021657.147016-1-briannorris@chromium.org>
Brian Norris <briannorris@chromium.org> wrote:
> Marvell folks tell me this is a debugging event that the driver doesn't
> need to handle, but on 8997 w/ firmware 16.68.1.p97, I see several of
> these sorts of messages at (for instance) boot time:
>
> [ 13.825848] mwifiex_pcie 0000:01:00.0: event: unknown event id: 0x63
> [ 14.838561] mwifiex_pcie 0000:01:00.0: event: unknown event id: 0x63
> [ 14.850397] mwifiex_pcie 0000:01:00.0: event: unknown event id: 0x63
> [ 32.529923] mwifiex_pcie 0000:01:00.0: event: unknown event id: 0x63
>
> Let's handle this "event" with a much lower verbosity.
>
> Signed-off-by: Brian Norris <briannorris@chromium.org>
Patch applied to wireless-drivers-next.git, thanks.
0ed917d09d51 mwifiex: don't complain about 'unknown event id: 0x63'
--
https://patchwork.kernel.org/patch/9516687/
Documentation about submitting wireless patches and checking status
from patchwork:
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2017-01-20 9:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-14 2:16 [PATCH] mwifiex: don't complain about 'unknown event id: 0x63' Brian Norris
2017-01-20 9:47 ` Kalle Valo [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=20170120094746.8FDEC609C9@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=akarwar@marvell.com \
--cc=briannorris@chromium.org \
--cc=cluo@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nishants@marvell.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).