netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Wed, 3 Jan 2024 13:21:20 -0800	[thread overview]
Message-ID: <20240103132120.2cace255@kernel.org> (raw)
In-Reply-To: <0aa87eb2-b50d-4ae8-81ce-af7a52813e6a@6wind.com>

On Wed, 3 Jan 2024 15:15:33 +0100 Nicolas Dichtel wrote:
> > The net-next added new function setup_ns in lib.sh and converted all hard code
> > netns setup. I think It may be good to post this patch set to net-next
> > to reduce future merge conflicts.  
> 
> The first patch is for net. I can post the second one to net-next if it eases
> the merge.
> 
> > Jakub, Paolo, please correct me if we can't post fixes to net-next.  
>
> Please, let me know if I should target net-next for the second patch.

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.

  reply	other threads:[~2024-01-03 21:21 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 [this message]
2024-01-04 13:51         ` Nicolas Dichtel
2024-01-04 15:17           ` Jakub Kicinski
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=20240103132120.2cace255@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).