All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Intel Linux Wireless <ilw@linux.intel.com>,
	linux-wireless@vger.kernel.org
Subject: Re: [RHEL6 PATCH] iwlwifi: remove spurious warning
Date: Mon, 9 Jul 2012 13:54:24 +0200	[thread overview]
Message-ID: <20120709115423.GE2438@redhat.com> (raw)
In-Reply-To: <1341834647.4455.32.camel@jlt3.sipsolutions.net>

On Mon, Jul 09, 2012 at 01:50:47PM +0200, Johannes Berg wrote:
> On Mon, 2012-07-09 at 13:48 +0200, Stanislaw Gruszka wrote:
> > BZ#837754
> > 
> > Description:
> > Some devices do not set SEQ_RX_FRAME flags for few commands that should
> > not be reclaimed. It was supposed to be fixed in firmware, but it was
> > not.
> > 
> > Upstream change also add possibility to configure which commands should
> > not be reclaimed, but that option is not used - only original 6 commands
> > are configured. So I did not backport that part, because it make things
> > somewhat (not necessarily) complex.
> 
> Yeah, looks fine. I'd hoped it was fixed for iwlwifi drivers (we
> couldn't remember if it was 4965 only or not) but it turns out it wasn't
> so this is needed.
> 
> I don't know if there's anything I should do about this though?

Sorry Johannes that was not intended to go to you and to the public.

Stanislaw

  reply	other threads:[~2012-07-09 11:54 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 [this message]
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
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=20120709115423.GE2438@redhat.com \
    --to=sgruszka@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.