From: Johannes Berg <johannes@sipsolutions.net>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Hilal Rahmatullah <hilalrahmatullah11@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Donald Hunter <donald.hunter@gmail.com>,
"open list:NETWORKING [GENERAL]" <netdev@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net v3] wifi: nl80211: document sta-info nested attribute
Date: Fri, 02 Oct 2026 22:30:36 +0200 [thread overview]
Message-ID: <649cc93941ed71c60d08151d8d13570f5e5319ef.camel@sipsolutions.net> (raw)
In-Reply-To: <20261002132500.0b71889b@kernel.org>
On Fri, 2026-10-02 at 13:25 -0700, Jakub Kicinski wrote:
> >
> > There's a license issue - we have ISC license on nl80211.h now, but
> > Donald and Hilal picked GPL/syscall/BSD-3 for the yaml and of course
>
> That license is required for all netlink specs, FWIW
> It's totally my fault if it's wrong, I just didn't want it to be
> _just_ GPL since that would propagate to use space code which
> we want to be permissive about. The spec is effectively a uAPI
> description it should be public domain in my non-layer mind.
Oh, sure. But BSD-3 isn't (advertising clause), and people copy at least
the nl80211.h file around to other projects. And the syscall exception
doesn't really talk about distributing that code. So presumably going
from ISC to this would require people to update even their binary
distribution's docs (where it's built in) ...
> > that carries over to the generated .h file, not sure if that's an issue
> > for downstream projects but might be with advertising clause? Could we
> > change it if I'm adding >10k new lines from nl80211.h? :)
> >
> > I can post it but ... is it worth it? Not even sure it would
> > significantly simplify our lives, although the generated header file
> > with documentation is much more regular in that it always has the type,
> > etc. (which is what Jouni was asking about)
>
> Well, I certainly don't care so my choice would be not to have to review
> the code gen changes (:
Fair :)
I'm not really sure it gives _that_ much benefit ... I guess I'll mull
it over and maybe run it by some wifi people.
Thanks :)
johannes
next prev parent reply other threads:[~2026-10-02 20:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-16 10:12 Hilal Rahmatullah
2026-08-17 15:47 ` Jakub Kicinski
2026-09-05 7:46 ` Johannes Berg
2026-10-02 17:34 ` Johannes Berg
2026-10-02 20:25 ` Jakub Kicinski
2026-10-02 20:30 ` Johannes Berg [this message]
2026-08-18 17:07 ` Jakub Kicinski
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=649cc93941ed71c60d08151d8d13570f5e5319ef.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=hilalrahmatullah11@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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
all inboxes | Powered by JetHome®