From: Jakub Kicinski <kuba@kernel.org>
To: Anders Roxell <anders.roxell@linaro.org>
Cc: shuah@kernel.org, willemb@google.com,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests: Makefile: add missing 'net/lib' to targets
Date: Thu, 12 Sep 2024 08:23:07 -0700 [thread overview]
Message-ID: <20240912082307.556db015@kernel.org> (raw)
In-Reply-To: <20240912063119.1277322-1-anders.roxell@linaro.org>
On Thu, 12 Sep 2024 08:31:18 +0200 Anders Roxell wrote:
> Fixes: 1d0dc857b5d8 ("selftests: drv-net: add checksum tests")
> Signed-off-by: Anders Roxell <anders.roxell@linaro.org>
> ---
> tools/testing/selftests/Makefile | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tools/testing/selftests/Makefile b/tools/testing/selftests/Makefile
> index 3b7df5477317..fc3681270afe 100644
> --- a/tools/testing/selftests/Makefile
> +++ b/tools/testing/selftests/Makefile
> @@ -64,6 +64,7 @@ TARGETS += net
> TARGETS += net/af_unix
> TARGETS += net/forwarding
> TARGETS += net/hsr
> +TARGETS += net/lib
> TARGETS += net/mptcp
> TARGETS += net/netfilter
> TARGETS += net/openvswitch
Please make sure you always include a commit message. Among other
things writing one would force you to understand the code, and
in this case understand that this target is intentionally left out.
Look around the Makefile for references to net/lib, you'll figure
it out.
The patch is incorrect.
next prev parent reply other threads:[~2024-09-12 15:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 6:31 [PATCH] selftests: Makefile: add missing 'net/lib' to targets Anders Roxell
2024-09-12 13:13 ` Willem de Bruijn
2024-09-12 15:23 ` Jakub Kicinski [this message]
2024-09-12 16:44 ` Shuah Khan
2024-09-15 6:44 ` Anders Roxell
2024-09-15 7:36 ` Willem de Bruijn
2024-09-15 14:46 ` Jakub Kicinski
2024-09-16 7:53 ` Anders Roxell
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=20240912082307.556db015@kernel.org \
--to=kuba@kernel.org \
--cc=anders.roxell@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=willemb@google.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