linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: "Jarek Kamiński" <Jarek@Freeside.be>,
	"Emmanuel Grumbach" <emmanuel.grumbach@intel.com>,
	"Intel Linux Wireless" <linuxwifi@intel.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Regression with Intel 3160 AP: client not reconnecting
Date: Fri, 24 Feb 2017 13:13:34 +0100	[thread overview]
Message-ID: <1487938414.2540.15.camel@sipsolutions.net> (raw)
In-Reply-To: <20170221213340.GA14974@Straylight.freeside.be> (sfid-20170221_224221_697139_D71C5101)

Hi Jarek,

[snip]

> What might be the cause? Is there anything I can do to help debug or
> fix this?

Thanks for the detailed bug report and analysis! I can't analyse this
in depth right now, can you please file a bug on bugzilla.kernel.org?

Thanks,
johannes

  reply	other threads:[~2017-02-24 12:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-21 21:33 Regression with Intel 3160 AP: client not reconnecting Jarek Kamiński
2017-02-24 12:13 ` Johannes Berg [this message]
2017-02-24 12:55   ` Jarek Kamiński
2017-02-26  6:57   ` Grumbach, Emmanuel

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=1487938414.2540.15.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=Jarek@Freeside.be \
    --cc=emmanuel.grumbach@intel.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linuxwifi@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).