From: Chris Down <chris@chrisdown.name>
To: linux-wireless@vger.kernel.org
Cc: Shahar S Matityahu <shahar.s.matityahu@intel.com>,
Luca Coelho <luciano.coelho@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iwlwifi: Don't IWL_WARN on FW reconfiguration
Date: Mon, 13 Jul 2020 12:51:37 +0100 [thread overview]
Message-ID: <20200713115137.GA1065134@chrisdown.name> (raw)
In-Reply-To: <20191017145321.GA1609@chrisdown.name>
Just to check in again since this is still happening: is this expected?
I expect that if this is IWL_WARN, it should indicate some unexpected or
non-ideal state, but the card seems to operate just fine afterwards.
next prev parent reply other threads:[~2020-07-13 11:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 14:48 [PATCH] iwlwifi: Don't IWL_WARN on FW reconfiguration Chris Down
2019-10-17 14:53 ` Chris Down
2020-07-13 11:51 ` Chris Down [this message]
2020-07-13 17:41 ` Johannes Hirte
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=20200713115137.GA1065134@chrisdown.name \
--to=chris@chrisdown.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luciano.coelho@intel.com \
--cc=shahar.s.matityahu@intel.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).