From: Jakub Kicinski <kuba@kernel.org>
To: Nicolas Dichtel <nicolas.dichtel@6wind.com>
Cc: Hangbin Liu <liuhangbin@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>, Phil Sutter <phil@nwl.cc>,
David Ahern <dsahern@kernel.org>,
netdev@vger.kernel.org
Subject: Re: [PATCH net v2 2/2] selftests: rtnetlink: check enslaving iface in a bond
Date: Thu, 4 Jan 2024 07:17:52 -0800 [thread overview]
Message-ID: <20240104071752.433651ce@kernel.org> (raw)
In-Reply-To: <4e1d5b11-6fec-4ee2-a091-479e480476be@6wind.com>
On Thu, 4 Jan 2024 14:51:08 +0100 Nicolas Dichtel wrote:
> > Looks like the patch applies to net-next, so hopefully there won't
> > be any actual conflicts. But it'd be good to follow up and refactor
> > it in net-next once net gets merged in. As long as I'm not missing
> > anything - up to you - I'm fine with either sending the test to
> > net-next like Hangbin suggests, or following up in net-next to use
> > setup_ns.
> I will send a follow-up once net gets merged in net-next.
Ack, there's still going to be a v3 to update the error message,
tho, right?
next prev parent reply other threads:[~2024-01-04 15:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 9:48 [PATCH net v2 0/2] rtnetlink: allow to enslave with one msg an up interface Nicolas Dichtel
2024-01-03 9:48 ` [PATCH net v2 1/2] rtnetlink: allow to set iface down before enslaving it Nicolas Dichtel
2024-01-03 15:38 ` David Ahern
2024-01-03 9:48 ` [PATCH net v2 2/2] selftests: rtnetlink: check enslaving iface in a bond Nicolas Dichtel
2024-01-03 13:00 ` Hangbin Liu
2024-01-03 14:15 ` Nicolas Dichtel
2024-01-03 21:21 ` Jakub Kicinski
2024-01-04 13:51 ` Nicolas Dichtel
2024-01-04 15:17 ` Jakub Kicinski [this message]
2024-01-04 16:39 ` Nicolas Dichtel
2024-01-03 15:42 ` David Ahern
2024-01-03 16:17 ` Nicolas Dichtel
2024-01-03 16:36 ` David Ahern
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=20240104071752.433651ce@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=liuhangbin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=pabeni@redhat.com \
--cc=phil@nwl.cc \
/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).