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: Tue, 6 Feb 2024 07:59:50 -0800 [thread overview]
Message-ID: <20240206075950.47d0bdc7@kernel.org> (raw)
In-Reply-To: <4342ac71-105f-4ed4-83b7-ede3ab7255f2@mojatatu.com>
On Mon, 5 Feb 2024 13:28:22 -0300 Victor Nogueira wrote:
> > We merge iproute2 into iprout2-next locally and build the combined
> > thing, FWIW. I haven't solved the problem of pending patches, yet,
> > tho :( If the iproute2-next patches are just on the list but not
> > merged the new tests will fail.
>
> In this case both were merged into -next trees. It's just the executor
> that needed fixing.
> For features merged into net-next but not yet in iproute2-next perhaps
> nipa can be used to catch such issues?
> Should I resend the patch now that the executor is fixed?
Sorry for the delay, I spent too much time migrating workers yesterday
to look at the list.
No need to resend, I'll revive it in patchwork. At least for now contest
keeps retesting the patches so we'll see in ~4h if all is good now.
About catching iproute - yes, we could so something similar to what we
do with netdev patches. Gather everything up from the list. Do basic
sanity checking of the patches. And make a "testing" version of
iproute2. A matter of having the time to do it :( Maybe the iproute2
maintainers would be willing to help?... :)
next prev parent reply other threads:[~2024-02-06 15:59 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
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 [this message]
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=20240206075950.47d0bdc7@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).