From: Johannes Berg <johannes@sipsolutions•net>
To: Sergey Matyukevich <geomatsi@gmail•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
Wireless <linux-wireless@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: build failure after merge of the mac80211-next tree
Date: Tue, 28 Apr 2020 09:46:37 +0200 [thread overview]
Message-ID: <40afd04ed8fb49088268e7d3316d3fef9aa8dbd9.camel@sipsolutions.net> (raw)
In-Reply-To: <20200428074527.GA3912@curiosity> (sfid-20200428_094101_668130_D6E3CFA4)
On Tue, 2020-04-28 at 10:45 +0300, Sergey Matyukevich wrote:
>
> Looks good. But I have a couple of questions:
>
> - why cleanup vif->mgmt_frame_reg in wilc_mac_open ?
Otherwise wilc_update_mgmt_frame_registrations() will think there are no
changes whatsoever, and do nothing.
> - previously wilc_wfi_p2p_rx was called only for PROBE_REQ and ACTION,
> now it will be called for all the other registred frames as well
Huh, good catch. How about this?
https://p.sipsolutions.net/51183f5492f05ea6.txt
johannes
next prev parent reply other threads:[~2020-04-28 7:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 2:29 linux-next: build failure after merge of the mac80211-next tree Stephen Rothwell
2020-04-28 7:01 ` Johannes Berg
2020-04-28 7:25 ` Sergey Matyukevich
2020-04-28 7:24 ` Johannes Berg
2020-04-28 7:45 ` Sergey Matyukevich
2020-04-28 7:46 ` Johannes Berg [this message]
2020-04-28 8:10 ` Sergey Matyukevich
-- strict thread matches above, loose matches on Subject: below --
2021-12-21 0:50 Stephen Rothwell
2021-12-21 11:02 ` Johannes Berg
2021-12-21 11:15 ` Stephen Rothwell
2021-12-21 11:17 ` Johannes Berg
2021-12-21 12:31 ` Kalle Valo
2020-11-11 1:24 Stephen Rothwell
2017-12-12 1:58 Stephen Rothwell
2017-12-12 8:46 ` Johannes Berg
[not found] ` <1513068419.26976.86.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2017-12-12 8:59 ` Toke Høiland-Jørgensen
2017-12-12 11:45 ` Kalle Valo
2017-12-12 13:24 ` Toke Høiland-Jørgensen
2016-02-24 0:59 Stephen Rothwell
2016-02-24 8:12 ` Johannes Berg
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=40afd04ed8fb49088268e7d3316d3fef9aa8dbd9.camel@sipsolutions.net \
--to=johannes@sipsolutions$(echo .)net \
--cc=geomatsi@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-wireless@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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