From: Jakub Kicinski <kuba@kernel.org>
To: Fernando Fernandez Mancera <fmancera@suse.de>
Cc: Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
horms@kernel.org, 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, 25 May 2026 09:08:55 -0700 [thread overview]
Message-ID: <20260525090855.43cf453a@kernel.org> (raw)
In-Reply-To: <7fb927ab-591c-4c07-9f85-31697b80a366@suse.de>
On Mon, 25 May 2026 17:53:04 +0200 Fernando Fernandez Mancera wrote:
> On 5/19/26 9:24 AM, Fernando Fernandez Mancera wrote:
> > On 5/19/26 9:17 AM, Paolo Abeni wrote:
> >> Ideally I think extending iproute2 would be the better solution.
> >> @Fernando: perhaps you could update the self-test accordingly, adding an
> >> explicit check for the iproute subcommand. If `ip netconf set` is not
> >> available skip the test, so that iproute2 patches could land later.
> >>
> >> Does the above look feasible?
> >>
> >
> > Yep. I agree. Okay, let's do that :-)
>
> As discussed in the thread, Jakub can you pick the other patches or
> should I repost the series without the selftest? I am now working on the
> iproute extension FWIW.
How long will the iproute2 extension take? If it's matter of days maybe
we should wait and base the selftest on it?
next prev parent reply other threads:[~2026-05-25 16:08 UTC|newest]
Thread overview: 20+ 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
2026-05-19 7:17 ` Paolo Abeni
2026-05-19 7:24 ` Fernando Fernandez Mancera
2026-05-25 15:53 ` Fernando Fernandez Mancera
2026-05-25 16:08 ` Jakub Kicinski [this message]
2026-05-25 17:12 ` 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=20260525090855.43cf453a@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 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.