From: Kalle Valo <kvalo@codeaurora.org>
To: Tony Lindgren <tony@atomide.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Eyal Reizer <eyalreizer@gmail.com>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org
Subject: Re: nl80211 wlcore regression in next
Date: Tue, 25 Jun 2019 12:18:39 +0300 [thread overview]
Message-ID: <87r27irpjk.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20190625080019.GH5447@atomide.com> (Tony Lindgren's message of "Tue, 25 Jun 2019 01:00:19 -0700")
Tony Lindgren <tony@atomide.com> writes:
> Hi,
>
> * Johannes Berg <johannes@sipsolutions.net> [190625 07:47]:
>> On Tue, 2019-06-25 at 00:38 -0700, Tony Lindgren wrote:
>> > Hi,
>> >
>> > Looks like at least drivers/net/wireless/ti wlcore driver has stopped
>> > working in Linux next with commit 901bb9891855 ("nl80211: require and
>> > validate vendor command policy"). Reverting the commit above makes it
>> > work again.
>> >
>> > It fails with the warning below, any ideas what goes wrong?
>>
>> Oops. For some reason, I neglected to check the vendor command usage
>> beyond hwsim.
>>
>> The patch below should work?
>
> Yeah thanks that fixes the issue for me:
>
> Tested-by: Tony Lindgren <tony@atomide.com>
Acked-by: Kalle Valo <kvalo@codeaurora.org>
--
Kalle Valo
prev parent reply other threads:[~2019-06-25 9:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 7:38 nl80211 wlcore regression in next Tony Lindgren
2019-06-25 7:46 ` Johannes Berg
2019-06-25 8:00 ` Tony Lindgren
2019-06-25 8:02 ` Johannes Berg
2019-06-25 8:56 ` Arend Van Spriel
2019-06-25 8:57 ` Johannes Berg
2019-07-22 13:02 ` Tony Lindgren
2019-07-23 5:07 ` Johannes Berg
2019-07-23 6:43 ` Tony Lindgren
2019-06-25 9:18 ` Kalle Valo [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=87r27irpjk.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=eyalreizer@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=tony@atomide.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).