From: Brian Norris <briannorris@chromium.org>
To: "Chadzynski, MikolajX" <mikolajx.chadzynski@intel.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"amitkarwar@gmail.com" <amitkarwar@gmail.com>,
"nishants@marvell.com" <nishants@marvell.com>,
"gbhat@marvell.com" <gbhat@marvell.com>,
"huxm@marvell.com" <huxm@marvell.com>
Subject: Re: porting 'mwifiex: resolve races between async FW init (failure) and device removal' to kernel 4.1.x
Date: Thu, 8 Jun 2017 13:00:56 -0700 [thread overview]
Message-ID: <20170608200055.GA109284@google.com> (raw)
In-Reply-To: <382E97DBE488D844B7F3CE8D1D2355C83717C8B6@IRSMSX104.ger.corp.intel.com>
On Thu, Jun 08, 2017 at 01:11:28PM +0000, Chadzynski, MikolajX wrote:
> Races between async firmware initialization and device removal appears on kernel 4.1.x.
> Whole scenario leading to the error together with logs is in https://bugzilla.kernel.org/show_bug.cgi?id=196003
> Mapping the patch from kernel 4.11.x "mwifiex: resolve races between async FW init (failure) and device removal" solved the problem.
FWIW, that patch was also in v4.10.
> In Bugzilla I've also attached patch which I've tested for pcie interface and it works.
What are you asking for? An official backport to the 4.1.x stable
series? I'm not super interested in trying to do that. And IIUC, your
patch is a no-go, as it will break the SDIO and USB driver builds.
If you do try to go forward with this, do try to note any follow-up
patches. I don't recall how many other related bugs there might have
been. I tried to mark things correctly with Fixes tags, but I may have
missed something, especially if such bugfixes also made it into 4.10.
Brian
prev parent reply other threads:[~2017-06-08 20:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 13:11 porting 'mwifiex: resolve races between async FW init (failure) and device removal' to kernel 4.1.x Chadzynski, MikolajX
2017-06-08 20:00 ` Brian Norris [this message]
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=20170608200055.GA109284@google.com \
--to=briannorris@chromium.org \
--cc=amitkarwar@gmail.com \
--cc=gbhat@marvell.com \
--cc=huxm@marvell.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mikolajx.chadzynski@intel.com \
--cc=nishants@marvell.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).