linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Clayton <chris2553@googlemail.com>
To: kvalo@codeaurora.org
Cc: linux-wireless@vger.kernel.org
Subject: IWLWIFI - 3.18-stable
Date: Sun, 11 Jan 2015 12:56:16 +0000	[thread overview]
Message-ID: <54B272F0.70307@googlemail.com> (raw)

Hi Kalle,

Having recently bought a new laptop, I've just started using the iwlwifi driver for wireless networking. I found both
3.18.x and the current development tree to be very unreliable due to frequent disconnections from the router.

Before you merged them into your tree, I grabbed the latest fixes from iwlwifi-fixes tree and applied them to the
development kernel. Since I did that I've had no problems at all with dropped connections. I then looked at each patch
to see whether it might be applicable to 3.18 and found that two of them looked as if they should be useful. They are:

c93edc639392df733c7d72db4376a9add775d18a - iwlwifi: mvm: don't allow diversity if BT Coex / TT forbid it

a9dc5060bf3a32ac3dad472f15416054b92dc5b5 - iwlwifi: mvm: fix out of bounds access to tid_to_mac80211_ac

With those two applied, I've had stable wireless networking on 3.18.2 and, more recently, 3.18.2. Consequently, they
seem appropriate for tagging for 3.18-stable, but, as far as I can see, they haven't been tagged for stable. Apologies,
if I'm mistaken, but if I'm not, could you consider submitting the two patches for inclusion in 3.18, please? Of course,
they may be appropriate to earlier kernels too - I haven't looked.

Thanks

Chris

             reply	other threads:[~2015-01-11 12:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-11 12:56 Chris Clayton [this message]
2015-01-11 13:00 ` IWLWIFI - 3.18-stable Chris Clayton
2015-01-11 14:16   ` Emmanuel Grumbach
2015-01-11 20:23     ` Chris Clayton
2015-01-12  6:03       ` Emmanuel Grumbach
2015-01-12 11:51         ` Chris Clayton
2015-01-12 12:20           ` 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=54B272F0.70307@googlemail.com \
    --to=chris2553@googlemail.com \
    --cc=kvalo@codeaurora.org \
    --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).