linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Arend van Spriel <arend.vanspriel@broadcom.com>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: net_device::destructor patch for brcmfmac
Date: Thu, 22 Jun 2017 13:02:30 +0300	[thread overview]
Message-ID: <871sqctk5l.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1498124992.2246.6.camel@sipsolutions.net> (Johannes Berg's message of "Thu, 22 Jun 2017 11:49:52 +0200")

Johannes Berg <johannes@sipsolutions.net> writes:

> 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.").

Is there a report from users or is this more like a theoretical issue?

We are quite late in 4.12 cycle so I would prefer to push this via
wireless-drivers-next and stable tree to 4.12.x, unless it's really
critical of course.

>> 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.

My plan is to send a pull request to Dave this week still (unless
Midsummer celebrations last too long, knowing Finland's weather that's
unlikely) and I could fast forward then. I have also other patches
waiting for stuff in net-next.

Arend, I think the best is that you use wireless-testing as baseline and
clearly document what commit your patch depends on. Once I have fast
forwarded wireless-drivers-next to latest net-next it _should_ apply
just fine.

-- 
Kalle Valo

  reply	other threads:[~2017-06-22 10:02 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
2017-06-22 10:02   ` Kalle Valo [this message]
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=871sqctk5l.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@codeaurora.org \
    --cc=arend.vanspriel@broadcom.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 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).