From: Jakub Kicinski <kuba@kernel.org>
To: Demos Ra via B4 Relay <devnull+demosthenes.ra.gmail.com@kernel.org>
Cc: demosthenes.ra@gmail.com, Donald Hunter <donald.hunter@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
David Ahern <dsahern@kernel.org>,
Ido Schimmel <idosch@nvidia.com>,
netdev@vger.kernel.org, Sashiko <sashiko-bot@kernel.org>
Subject: Re: [PATCH net 0/2] tools: ynl: generate code for rt-nexthop bucket notifications
Date: Mon, 26 Oct 2026 15:59:12 -0700 [thread overview]
Message-ID: <20261026155912.3f357085@kernel.org> (raw)
In-Reply-To: <20261025-ynl-ntf-bucket-v1-0-65aef308d62c@gmail.com>
On Sun, 25 Oct 2026 00:13:54 +0700 Demos Ra via B4 Relay wrote:
> Commit 457dc9fefe9a ("netlink: specs: Add a spec for nexthops in
> rtnetlink") left newnexthopbucket-ntf out of the C code generation,
> because ynl-gen could not write a notification table entry for it.
> Sashiko pointed out that the generated library then fails at runtime
> when the kernel sends that notification to a subscribed socket.
>
> Patch 1 lets ynl-gen handle a classic notification that no request
> matches. Patch 2 drops the exclusion.
>
> 457dc9fefe9a was pulled in this merge window, hence net.
Unsupported functionality is not a bug. I suspect you just fed
the Sashiko report to an LLM and posted the output.
--
pw-bot: defer
next prev parent reply other threads:[~2026-10-26 22:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-24 17:13 [PATCH net 0/2] tools: ynl: generate code for rt-nexthop bucket notifications Demos Ra via B4 Relay
2026-10-24 17:13 ` [PATCH net 1/2] tools: ynl-gen-c: handle classic notifications without a matching request Demos Ra via B4 Relay
2026-10-24 17:13 ` [PATCH net 2/2] tools: ynl: generate code for rt-nexthop bucket notifications Demos Ra via B4 Relay
2026-10-26 22:59 ` Jakub Kicinski [this message]
2026-10-27 1:29 ` [PATCH net 0/2] " Demos Ra
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=20261026155912.3f357085@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=demosthenes.ra@gmail.com \
--cc=devnull+demosthenes.ra.gmail.com@kernel.org \
--cc=donald.hunter@gmail.com \
--cc=dsahern@kernel.org \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sashiko-bot@kernel.org \
/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