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, jiri@resnulli.us,
nicolas.dichtel@6wind.com, willemb@google.com,
Jakub Kicinski <kuba@kernel.org>
Subject: [PATCH net 0/3] tools: ynl: fix header guards and impossible errors
Date: Fri, 16 Feb 2024 16:17:39 -0800 [thread overview]
Message-ID: <20240217001742.2466993-1-kuba@kernel.org> (raw)
Fix header guards for new families. I must have installed the latest
headers on my system when I was developing. Now it seems system update
overwrote them back to something slightly older, revealing the guards
I put in are wrong.
Also fix bugs discovered while I was hacking in low level stuff in YNL
and kept breaking the socket, really exercising the "impossible" paths.
Jakub Kicinski (3):
tools: ynl: fix header guards
tools: ynl: make sure we always pass yarg to mnl_cb_run
tools: ynl: don't leak mcast_groups on init error
tools/net/ynl/Makefile.deps | 4 ++--
tools/net/ynl/lib/ynl.c | 19 +++++++++++++++----
2 files changed, 17 insertions(+), 6 deletions(-)
--
2.43.0
next reply other threads:[~2024-02-17 0:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-17 0:17 Jakub Kicinski [this message]
2024-02-17 0:17 ` [PATCH net 1/3] tools: ynl: fix header guards Jakub Kicinski
2024-02-19 17:18 ` Nicolas Dichtel
2024-02-17 0:17 ` [PATCH net 2/3] tools: ynl: make sure we always pass yarg to mnl_cb_run Jakub Kicinski
2024-02-19 17:18 ` Nicolas Dichtel
2024-02-17 0:17 ` [PATCH net 3/3] tools: ynl: don't leak mcast_groups on init error Jakub Kicinski
2024-02-19 17:19 ` Nicolas Dichtel
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=20240217001742.2466993-1-kuba@kernel.org \
--to=kuba@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=pabeni@redhat.com \
--cc=willemb@google.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.