From: Jakub Kicinski <kuba@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,
pabeni@redhat.com, edumazet@google.com,
linux-kselftest@vger.kernel.org, bpf@vger.kernel.org,
llvm@lists.linux.dev, Davide Caratti <dcaratti@redhat.com>
Subject: Re: [PATCH net-next 1/5] selftests: tc-testing: remove buildebpf plugin
Date: Mon, 27 Nov 2023 18:15:27 -0800 [thread overview]
Message-ID: <20231127181527.1101e015@kernel.org> (raw)
In-Reply-To: <20231124154248.315470-2-pctammela@mojatatu.com>
On Fri, 24 Nov 2023 12:42:44 -0300 Pedro Tammela wrote:
> diff --git a/tools/testing/selftests/tc-testing/Makefile b/tools/testing/selftests/tc-testing/Makefile
> index b1fa2e177e2f..e8b3dde4fa16 100644
> --- a/tools/testing/selftests/tc-testing/Makefile
> +++ b/tools/testing/selftests/tc-testing/Makefile
> @@ -1,31 +1,6 @@
> # SPDX-License-Identifier: GPL-2.0
> -include ../../../scripts/Makefile.include
>
> -top_srcdir = $(abspath ../../../..)
> -APIDIR := $(top_scrdir)/include/uapi
> -TEST_GEN_FILES = action.o
> +TEST_PROGS += ./tdc.sh
nit: could you try to remove the ./ prefix, as a follow up?
I think it's not necessary and it confuses one of patchwork checks.
next prev parent reply other threads:[~2023-11-28 2:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 15:42 [PATCH net-next 0/5] selftests: tc-testing: updates and cleanups for tdc Pedro Tammela
2023-11-24 15:42 ` [PATCH net-next 1/5] selftests: tc-testing: remove buildebpf plugin Pedro Tammela
2023-11-28 2:15 ` Jakub Kicinski [this message]
2023-11-24 15:42 ` [PATCH net-next 2/5] selftests: tc-testing: remove unnecessary time.sleep Pedro Tammela
2023-11-24 15:42 ` [PATCH net-next 3/5] selftests: tc-testing: prefix iproute2 functions with "ipr2" Pedro Tammela
2023-11-24 15:42 ` [PATCH net-next 4/5] selftests: tc-testing: cleanup on Ctrl-C Pedro Tammela
2023-11-24 15:42 ` [PATCH net-next 5/5] selftests: tc-testing: remove unused import Pedro Tammela
2023-11-27 15:48 ` [PATCH net-next 0/5] selftests: tc-testing: updates and cleanups for tdc Jamal Hadi Salim
2023-11-28 2:20 ` 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=20231127181527.1101e015@kernel.org \
--to=kuba@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=dcaratti@redhat.com \
--cc=edumazet@google.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=linux-kselftest@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pctammela@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).