From: Jakub Kicinski <kuba@kernel.org>
To: Fernando Fernandez Mancera <fmancera@suse.de>
Cc: netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
horms@kernel.org, pabeni@redhat.com, edumazet@google.com,
dsahern@kernel.org, davem@davemloft.net
Subject: Re: [PATCH 3/3 net-next v4] selftests: net: add test for IPv4 devconf netlink notifications
Date: Mon, 18 May 2026 14:23:46 -0700 [thread overview]
Message-ID: <20260518142346.4c0903de@kernel.org> (raw)
In-Reply-To: <f5cae72f-93c7-41d7-b7db-2b60281afb72@suse.de>
On Sat, 16 May 2026 09:02:27 +0200 Fernando Fernandez Mancera wrote:
> >> Oh sorry, I should have clarified it. ip netconf only shows/query them
> >> but it cannot set them AFAICS.
> >>
> >> Usage: ip netconf show [ dev STRING ]
> >
> > Oh, fun. anyway, you gotta find a better way. Or just give up on the
> > selftest, the YNL hack is too ugly to live
> >
>
> Fair, let me see what I can do. Otherwise, Paolo as you requested the
> selftest, would it be acceptable for you to drop it given the situation?
> I looking for alternatives anyway :-)
Maybe extend iproute2 ?
next prev parent reply other threads:[~2026-05-18 21:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-10 8:15 [PATCH 1/3 net-next v4] ipv4: centralize devconf sysctl handling Fernando Fernandez Mancera
2026-05-10 8:15 ` [PATCH 2/3 net-next v4] ipv4: handle devconf post-set actions on netlink updates Fernando Fernandez Mancera
2026-05-14 2:30 ` Jakub Kicinski
2026-05-14 9:16 ` Fernando Fernandez Mancera
2026-05-10 8:15 ` [PATCH 3/3 net-next v4] selftests: net: add test for IPv4 devconf netlink notifications Fernando Fernandez Mancera
2026-05-14 2:35 ` Jakub Kicinski
2026-05-14 9:42 ` Fernando Fernandez Mancera
2026-05-14 23:24 ` Jakub Kicinski
2026-05-15 8:02 ` Fernando Fernandez Mancera
2026-05-16 1:16 ` Jakub Kicinski
2026-05-16 7:02 ` Fernando Fernandez Mancera
2026-05-18 21:23 ` Jakub Kicinski [this message]
2026-05-19 7:17 ` Paolo Abeni
2026-05-19 7:24 ` Fernando Fernandez Mancera
2026-05-19 13:45 ` Nicolas Dichtel
2026-05-19 21:27 ` Fernando Fernandez Mancera
2026-05-20 7:22 ` 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=20260518142346.4c0903de@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=fmancera@suse.de \
--cc=horms@kernel.org \
--cc=linux-kselftest@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