From: Johannes Berg <johannes@sipsolutions.net>
To: Arend van Spriel <arend.vanspriel@broadcom.com>,
Kalle Valo <kvalo@codeaurora.org>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: net_device::destructor patch for brcmfmac
Date: Thu, 22 Jun 2017 11:49:52 +0200 [thread overview]
Message-ID: <1498124992.2246.6.camel@sipsolutions.net> (raw)
In-Reply-To: <3f81fbd3-2896-2b09-1d59-ae5ec88045c9@broadcom.com> (sfid-20170622_114530_618693_3E9C66A1)
On Thu, 2017-06-22 at 11:45 +0200, Arend van Spriel wrote:
> Hi Kalle,
>
> I have a fix for brcmfmac, which is related to a change Dave made in
> struct net_device, ie. commit cf124db566e6 ("net: Fix inconsistent
> teardown and release of private netdev state."). This change is not
> in
> wireless-drivers-next, but it is in mac80211-next and thus in
> wireless-testing. What should I do? Submit to net-next, or
> mac80211-next, or will you merge net-next into wireless-drivers-next?
Actually, it's even in *net* I believe, so you should submit it to
there, or Kalle should integrate (fast-forward, rebase?) that into
wireless-drivers.
johannes
next prev parent reply other threads:[~2017-06-22 9:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 9:45 net_device::destructor patch for brcmfmac Arend van Spriel
2017-06-22 9:49 ` Johannes Berg [this message]
2017-06-22 10:02 ` Kalle Valo
2017-06-22 10:07 ` Arend van Spriel
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=1498124992.2246.6.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend.vanspriel@broadcom.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).