Hi Johannes,
Is there any sort of release cadence to the iw tool? Or is it pretty
arbitrary? I'm curious, since it's been more than a year since the
"v4.14" release. I'd like to package up bugfixes and a few features,
but it'd be much nicer to just pull a new official tag/tarball than to
drop a bunch of individual patches into my build system. If you're
going to tag something soon though, I can...just wait for you :)
More bluntly: can I haz release please?
Regards,
Brian
Hi Brian,
> Is there any sort of release cadence to the iw tool? Or is it pretty
> arbitrary?
It's completely arbitrary. I tried to follow kernel releases, but as you
can see I just haven't kept up ...
> I'm curious, since it's been more than a year since the
> "v4.14" release. I'd like to package up bugfixes and a few features,
> but it'd be much nicer to just pull a new official tag/tarball than to
> drop a bunch of individual patches into my build system. If you're
> going to tag something soon though, I can...just wait for you :)
>
> More bluntly: can I haz release please?
Sure!
I'll just tag one now :-)
johannes
On Fri, 2019-02-01 at 22:54 +0100, Johannes Berg wrote:
>
> I'll just tag one now :-)
Done. I updated a few things and pulled in our FTM support code too, now
that all the nl80211.h api is upstream.
johannes
On Fri, Feb 1, 2019 at 2:09 PM Johannes Berg <[email protected]> wrote:
> On Fri, 2019-02-01 at 22:54 +0100, Johannes Berg wrote:
> >
> > I'll just tag one now :-)
>
> Done. I updated a few things and pulled in our FTM support code too, now
> that all the nl80211.h api is upstream.
Awesome, thanks! Presumably a tarball is on its way?
Brian
On Fri, 2019-02-01 at 14:17 -0800, Brian Norris wrote:
> On Fri, Feb 1, 2019 at 2:09 PM Johannes Berg <[email protected]> wrote:
> > On Fri, 2019-02-01 at 22:54 +0100, Johannes Berg wrote:
> > >
> > > I'll just tag one now :-)
> >
> > Done. I updated a few things and pulled in our FTM support code too, now
> > that all the nl80211.h api is upstream.
>
> Awesome, thanks! Presumably a tarball is on its way?
Need to figure out how to use kup again ...
johannes
On Fri, 2019-02-01 at 23:18 +0100, Johannes Berg wrote:
> On Fri, 2019-02-01 at 14:17 -0800, Brian Norris wrote:
> > On Fri, Feb 1, 2019 at 2:09 PM Johannes Berg <[email protected]> wrote:
> > > On Fri, 2019-02-01 at 22:54 +0100, Johannes Berg wrote:
> > > >
> > > > I'll just tag one now :-)
> > >
> > > Done. I updated a few things and pulled in our FTM support code too, now
> > > that all the nl80211.h api is upstream.
> >
> > Awesome, thanks! Presumably a tarball is on its way?
>
> Need to figure out how to use kup again ...
Ok I think I figured it out, but it takes a little while to sync and be
visible on the public frontend.
johannes
On Fri, Feb 1, 2019 at 2:23 PM Johannes Berg <[email protected]> wrote:
>
> On Fri, 2019-02-01 at 23:18 +0100, Johannes Berg wrote:
> > On Fri, 2019-02-01 at 14:17 -0800, Brian Norris wrote:
> > > On Fri, Feb 1, 2019 at 2:09 PM Johannes Berg <[email protected]> wrote:
> > > > On Fri, 2019-02-01 at 22:54 +0100, Johannes Berg wrote:
> > > > >
> > > > > I'll just tag one now :-)
> > > >
> > > > Done. I updated a few things and pulled in our FTM support code too, now
> > > > that all the nl80211.h api is upstream.
> > >
> > > Awesome, thanks! Presumably a tarball is on its way?
> >
> > Need to figure out how to use kup again ...
>
> Ok I think I figured it out, but it takes a little while to sync and be
> visible on the public frontend.
>
One more 'I can haz release plz' nag.
Support for 11ax MCS rates and HE stuff came after 5.0.1, and
preferably we should take that with an upstream uprev not local
patches applied on top of 5.0.1?
https://git.kernel.org/pub/scm/linux/kernel/git/jberg/iw.git/log/
Thanks in advance!
> johannes
>