From: Stanislav Fomichev <sdf@google.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, Stanislav Fomichev <sdf@google.com>
Subject: [PATCH net-next v2 0/4] ynl: couple of unrelated fixes
Date: Thu, 27 Jul 2023 09:29:57 -0700 [thread overview]
Message-ID: <20230727163001.3952878-1-sdf@google.com> (raw)
- spelling of xdp-features
- s/xdp_zc_max_segs/xdp-zc-max-segs/
- expose xdp-zc-max-segs
- add /* private: */
- regenerate headers
- print xdp_zc_max_segs from sample
v2:
- don't put newline after /* private: */ (Jakub)
- use ynl-regen.sh for regen (Jakub)
Stanislav Fomichev (4):
ynl: expose xdp-zc-max-segs
ynl: mark max/mask as private for kdoc
ynl: regenerate all headers
ynl: print xdp-zc-max-segs in the sample
Documentation/netlink/specs/netdev.yaml | 5 +++--
include/uapi/linux/netdev.h | 3 ++-
tools/include/uapi/linux/netdev.h | 3 ++-
tools/net/ynl/Makefile | 1 +
tools/net/ynl/generated/netdev-user.c | 6 ++++++
tools/net/ynl/generated/netdev-user.h | 2 ++
tools/net/ynl/samples/netdev.c | 2 ++
tools/net/ynl/ynl-gen-c.py | 1 +
tools/net/ynl/ynl-regen.sh | 5 +++++
9 files changed, 24 insertions(+), 4 deletions(-)
--
2.41.0.487.g6d72f3e995-goog
next reply other threads:[~2023-07-27 16:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 16:29 Stanislav Fomichev [this message]
2023-07-27 16:29 ` [PATCH net-next v2 1/4] ynl: expose xdp-zc-max-segs Stanislav Fomichev
2023-07-27 16:29 ` [PATCH net-next v2 2/4] ynl: mark max/mask as private for kdoc Stanislav Fomichev
2023-07-27 16:30 ` [PATCH net-next v2 3/4] ynl: regenerate all headers Stanislav Fomichev
2023-07-27 16:30 ` [PATCH net-next v2 4/4] ynl: print xdp-zc-max-segs in the sample Stanislav Fomichev
2023-07-27 16:49 ` [PATCH net-next v2 0/4] ynl: couple of unrelated fixes Jakub Kicinski
2023-07-28 16:50 ` 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=20230727163001.3952878-1-sdf@google.com \
--to=sdf@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@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;
as well as URLs for NNTP newsgroup(s).