netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Victor Nogueira <victor@mojatatu.com>
Cc: jhs@mojatatu.com, xiyou.wangcong@gmail.com, davem@davemloft.net,
	edumazet@google.com, pabeni@redhat.com, netdev@vger.kernel.org,
	kernel@mojatatu.com, pctammela@mojatatu.com
Subject: Re: [PATCH net-next] selftests: tc-testing: add mirred to block tdc tests
Date: Fri, 2 Feb 2024 21:00:25 -0800	[thread overview]
Message-ID: <20240202210025.555deef9@kernel.org> (raw)
In-Reply-To: <20240202020726.529170-1-victor@mojatatu.com>

On Thu,  1 Feb 2024 23:07:26 -0300 Victor Nogueira wrote:
> Add 8 new mirred tdc tests that target mirred to block:
> 
> - Add mirred mirror to egress block action
> - Add mirred mirror to ingress block action
> - Add mirred redirect to egress block action
> - Add mirred redirect to ingress block action
> - Try to add mirred action with both dev and block
> - Try to add mirred action without specifying neither dev nor block
> - Replace mirred redirect to dev action with redirect to block
> - Replace mirred redirect to block action with mirror to dev

I think this breaks the TDC runner.
I'll toss it from patchwork, I can revive it when TDC is fixed (or you
tell me that I'm wrong).

  reply	other threads:[~2024-02-03  5:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-02  2:07 [PATCH net-next] selftests: tc-testing: add mirred to block tdc tests Victor Nogueira
2024-02-03  5:00 ` Jakub Kicinski [this message]
2024-02-03 20:15   ` Victor Nogueira
2024-02-04 16:33     ` Jakub Kicinski
2024-02-05 16:28       ` Victor Nogueira
2024-02-06 15:59         ` Jakub Kicinski
2024-02-28 16:49           ` Naresh Kamboju
2024-02-28 17:35             ` Victor Nogueira
2024-02-28 20:35               ` Naresh Kamboju
2024-02-09 20: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=20240202210025.555deef9@kernel.org \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jhs@mojatatu.com \
    --cc=kernel@mojatatu.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pctammela@mojatatu.com \
    --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).