From: Jakub Kicinski <kuba@kernel.org>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, edumazet@google.com, pabeni@redhat.com,
chuck.lever@oracle.com, Jakub Kicinski <kuba@kernel.org>
Subject: [PATCH net 0/3] ynl: another license adjustment
Date: Wed, 15 Mar 2023 16:03:48 -0700 [thread overview]
Message-ID: <20230315230351.478320-1-kuba@kernel.org> (raw)
Hopefully the last adjustment to the licensing of the specs.
I'm still the author so should be fine to do this.
Jakub Kicinski (3):
tools: ynl: make definitions optional again
ynl: broaden the license even more
ynl: make the tooling check the license
Documentation/netlink/genetlink-c.yaml | 2 +-
Documentation/netlink/genetlink-legacy.yaml | 2 +-
Documentation/netlink/genetlink.yaml | 2 +-
Documentation/netlink/specs/ethtool.yaml | 2 +-
Documentation/netlink/specs/fou.yaml | 2 +-
Documentation/netlink/specs/netdev.yaml | 2 +-
Documentation/userspace-api/netlink/specs.rst | 3 ++-
include/uapi/linux/fou.h | 2 +-
include/uapi/linux/netdev.h | 2 +-
net/core/netdev-genl-gen.c | 2 +-
net/core/netdev-genl-gen.h | 2 +-
net/ipv4/fou_nl.c | 2 +-
net/ipv4/fou_nl.h | 2 +-
tools/include/uapi/linux/netdev.h | 2 +-
tools/net/ynl/lib/nlspec.py | 11 ++++++++++-
tools/net/ynl/ynl-gen-c.py | 15 ++++++++-------
16 files changed, 33 insertions(+), 22 deletions(-)
--
2.39.2
next reply other threads:[~2023-03-15 23:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 23:03 Jakub Kicinski [this message]
2023-03-15 23:03 ` [PATCH net 1/3] tools: ynl: make definitions optional again Jakub Kicinski
2023-03-15 23:03 ` [PATCH net 2/3] ynl: broaden the license even more Jakub Kicinski
2023-03-15 23:03 ` [PATCH net 3/3] ynl: make the tooling check the license Jakub Kicinski
2023-03-15 23:53 ` [PATCH net 0/3] ynl: another license adjustment Chuck Lever III
2023-03-17 4:30 ` patchwork-bot+netdevbpf
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=20230315230351.478320-1-kuba@kernel.org \
--to=kuba@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--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 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.