Linux-Wireless Archive on lore.kernel.org
 help / color / Atom feed
* iw release cadence?
@ 2019-02-01 21:46 Brian Norris
  2019-02-01 21:54 ` Johannes Berg
  0 siblings, 1 reply; 7+ messages in thread
From: Brian Norris @ 2019-02-01 21:46 UTC (permalink / raw)
  To: Johannes Berg; +Cc: linux-wireless

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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: iw release cadence?
  2019-02-01 21:46 iw release cadence? Brian Norris
@ 2019-02-01 21:54 ` Johannes Berg
  2019-02-01 22:09   ` Johannes Berg
  0 siblings, 1 reply; 7+ messages in thread
From: Johannes Berg @ 2019-02-01 21:54 UTC (permalink / raw)
  To: Brian Norris; +Cc: linux-wireless

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


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: iw release cadence?
  2019-02-01 21:54 ` Johannes Berg
@ 2019-02-01 22:09   ` Johannes Berg
  2019-02-01 22:17     ` Brian Norris
  0 siblings, 1 reply; 7+ messages in thread
From: Johannes Berg @ 2019-02-01 22:09 UTC (permalink / raw)
  To: Brian Norris; +Cc: linux-wireless

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


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: iw release cadence?
  2019-02-01 22:09   ` Johannes Berg
@ 2019-02-01 22:17     ` Brian Norris
  2019-02-01 22:18       ` Johannes Berg
  0 siblings, 1 reply; 7+ messages in thread
From: Brian Norris @ 2019-02-01 22:17 UTC (permalink / raw)
  To: Johannes Berg; +Cc: linux-wireless

On Fri, Feb 1, 2019 at 2:09 PM Johannes Berg <johannes@sipsolutions.net> 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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: iw release cadence?
  2019-02-01 22:17     ` Brian Norris
@ 2019-02-01 22:18       ` Johannes Berg
  2019-02-01 22:23         ` Johannes Berg
  0 siblings, 1 reply; 7+ messages in thread
From: Johannes Berg @ 2019-02-01 22:18 UTC (permalink / raw)
  To: Brian Norris; +Cc: linux-wireless

On Fri, 2019-02-01 at 14:17 -0800, Brian Norris wrote:
> On Fri, Feb 1, 2019 at 2:09 PM Johannes Berg <johannes@sipsolutions.net> 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


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: iw release cadence?
  2019-02-01 22:18       ` Johannes Berg
@ 2019-02-01 22:23         ` Johannes Berg
  2019-08-04 22:25           ` Kirtika Ruchandani
  0 siblings, 1 reply; 7+ messages in thread
From: Johannes Berg @ 2019-02-01 22:23 UTC (permalink / raw)
  To: Brian Norris; +Cc: linux-wireless

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 <johannes@sipsolutions.net> 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


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: iw release cadence?
  2019-02-01 22:23         ` Johannes Berg
@ 2019-08-04 22:25           ` Kirtika Ruchandani
  0 siblings, 0 replies; 7+ messages in thread
From: Kirtika Ruchandani @ 2019-08-04 22:25 UTC (permalink / raw)
  To: Johannes Berg; +Cc: Brian Norris, linux-wireless, npoojary

On Fri, Feb 1, 2019 at 2:23 PM Johannes Berg <johannes@sipsolutions.net> 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 <johannes@sipsolutions.net> 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
>

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, back to index

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-02-01 21:46 iw release cadence? Brian Norris
2019-02-01 21:54 ` Johannes Berg
2019-02-01 22:09   ` Johannes Berg
2019-02-01 22:17     ` Brian Norris
2019-02-01 22:18       ` Johannes Berg
2019-02-01 22:23         ` Johannes Berg
2019-08-04 22:25           ` Kirtika Ruchandani

Linux-Wireless Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-wireless/0 linux-wireless/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-wireless linux-wireless/ https://lore.kernel.org/linux-wireless \
		linux-wireless@vger.kernel.org linux-wireless@archiver.kernel.org
	public-inbox-index linux-wireless


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-wireless


AGPL code for this site: git clone https://public-inbox.org/ public-inbox