From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Emmanuel Grumbach <egrumbach@gmail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Intel Linux Wireless <ilw@linux.intel.com>,
linux-wireless@vger.kernel.org
Subject: Re: [RHEL6 PATCH] iwlwifi: remove spurious warning
Date: Tue, 10 Jul 2012 15:37:09 +0200 [thread overview]
Message-ID: <20120710133708.GC2260@redhat.com> (raw)
In-Reply-To: <CANUX_P3Vh1pqyK7TnNdYPS6nHpiUEzWDr4j8+8a5kXdhY3DrAA@mail.gmail.com>
On Tue, Jul 10, 2012 at 04:15:09PM +0300, Emmanuel Grumbach wrote:
> Emmanuel Grumbach
> egrumbach@gmail.com
>
>
> On Tue, Jul 10, 2012 at 9:02 AM, Stanislaw Gruszka <sgruszka@redhat.com> wrote:
> > On Mon, Jul 09, 2012 at 10:10:38PM +0300, Emmanuel Grumbach wrote:
> >> I would be glad to know on what commands this WARN_ON triggers
> >> though... The command name should be printed along with the WARN_ON.
> >
> > REPLY_RX_PHY_CMD
> >
>
> Ok thanks. This comes from the fw for every HT frame received in 4965.
> Do you see that the WARNING triggers for every HT frame Rx?
> I don't mind removing that code anyway, I was just asking to
> understand what happens :-)
I did not hit that. It was raported for iwl1000 on RHEL6.3:
https://bugzilla.redhat.com/show_bug.cgi?id=837754
Stanislaw
next prev parent reply other threads:[~2012-07-10 13:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 11:48 [RHEL6 PATCH] iwlwifi: remove spurious warning Stanislaw Gruszka
2012-07-09 11:50 ` Johannes Berg
2012-07-09 11:54 ` Stanislaw Gruszka
2012-07-09 19:10 ` Emmanuel Grumbach
2012-07-10 6:02 ` Stanislaw Gruszka
2012-07-10 13:15 ` Emmanuel Grumbach
2012-07-10 13:37 ` Stanislaw Gruszka [this message]
2012-07-10 20:38 ` Emmanuel Grumbach
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=20120710133708.GC2260@redhat.com \
--to=sgruszka@redhat.com \
--cc=egrumbach@gmail.com \
--cc=ilw@linux.intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@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).