From: Simon Horman <horms@kernel.org>
To: Pedro Tammela <pctammela@mojatatu.com>
Cc: netdev@vger.kernel.org, jhs@mojatatu.com,
xiyou.wangcong@gmail.com, jiri@resnulli.us, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
shuah@kernel.org, victor@mojatatu.com
Subject: Re: [PATCH net-next 1/4] selftests: tc-testing: drop '-N' argument from nsPlugin
Date: Thu, 16 Nov 2023 14:08:02 +0000 [thread overview]
Message-ID: <20231116140802.GA109951@vergenet.net> (raw)
In-Reply-To: <20231114160442.1023815-2-pctammela@mojatatu.com>
On Tue, Nov 14, 2023 at 01:04:39PM -0300, Pedro Tammela wrote:
> This argument would bypass the net namespace creation and run the test in
> the root namespace, even if nsPlugin was specified.
> Drop it as it's the same as commenting out the nsPlugin from a test and adds
> additional complexity to the plugin code.
>
> Signed-off-by: Pedro Tammela <pctammela@mojatatu.com>
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2023-11-16 14:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 16:04 [PATCH net-next 0/4] selftests: tc-testing: updates to tdc Pedro Tammela
2023-11-14 16:04 ` [PATCH net-next 1/4] selftests: tc-testing: drop '-N' argument from nsPlugin Pedro Tammela
2023-11-16 14:08 ` Simon Horman [this message]
2023-11-14 16:04 ` [PATCH net-next 2/4] selftests: tc-testing: rework namespaces and devices setup Pedro Tammela
2023-11-16 14:11 ` Simon Horman
2023-11-14 16:04 ` [PATCH net-next 3/4] selftests: tc-testing: preload all modules in kselftests Pedro Tammela
2023-11-16 14:12 ` Simon Horman
2023-11-14 16:04 ` [PATCH net-next 4/4] selftests: tc-testing: use parallel tdc " Pedro Tammela
2023-11-16 14:12 ` Simon Horman
2023-11-15 16:39 ` [PATCH net-next 0/4] selftests: tc-testing: updates to tdc Jamal Hadi Salim
2023-11-16 22:40 ` patchwork-bot+netdevbpf
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=20231116140802.GA109951@vergenet.net \
--to=horms@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pctammela@mojatatu.com \
--cc=shuah@kernel.org \
--cc=victor@mojatatu.com \
--cc=xiyou.wangcong@gmail.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;
as well as URLs for NNTP newsgroup(s).