From: Tony Lindgren <tony@atomide.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Kalle Valo <kvalo@codeaurora.org>,
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: Mon, 22 Jul 2019 06:02:13 -0700 [thread overview]
Message-ID: <20190722130213.GN5447@atomide.com> (raw)
In-Reply-To: <7f74087fef1e554e0aeb82a6cec4113727487928.camel@sipsolutions.net>
Hi,
* Johannes Berg <johannes@sipsolutions.net> [190625 08:03]:
> On Tue, 2019-06-25 at 01:00 -0700, Tony Lindgren wrote:
> > 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>
>
> Thanks, I'll drop that into my tree and hopefully will remember to send
> it on soon.
Looks like this one crept back as the fix is missing from v5.3-rc1.
Forgot to include in the pull request?
Regards,
Tony
next prev parent reply other threads:[~2019-07-22 13:02 UTC|newest]
Thread overview: 13+ 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
[not found] ` <2570f4087d6e3356df34635a0380ec8ce06c9159.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2019-06-25 8:00 ` Tony Lindgren
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 [this message]
[not found] ` <20190722130213.GN5447-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2019-07-23 5:07 ` Johannes Berg
2019-07-23 5:07 ` Johannes Berg
2019-07-23 6:43 ` Tony Lindgren
[not found] ` <20190625080019.GH5447-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2019-06-25 9:18 ` Kalle Valo
2019-06-25 9:18 ` Kalle Valo
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=20190722130213.GN5447@atomide.com \
--to=tony@atomide.com \
--cc=eyalreizer@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.