From: David Hunter <david.hunter.linux@gmail.com>
To: david.hunter.linux@gmail.com
Cc: davem@davemloft.net, edumazet@google.com,
javier.carrasco.cruz@gmail.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com, shuah@kernel.org
Subject: [PATCH 1/1 V2] Selftests: net: Set executable bit for shell script
Date: Sat, 24 Aug 2024 10:38:37 -0400 [thread overview]
Message-ID: <20240824143837.228874-1-david.hunter.linux@gmail.com> (raw)
In-Reply-To: <20240823190828.214443-1-david.hunter.linux@gmail.com>
Turn on the execution bit for the shell script file. The test is skipped
when downloaded from the linux_mainline source files.
Signed-off-by: David Hunter <david.hunter.linux@gmail.com>
---
V1 --> V2
- Split the patch into two separate patches (one for each issue)
- Included subject prefixes
---
tools/testing/selftests/net/test_ingress_egress_chaining.sh | 0
1 file changed, 0 insertions(+), 0 deletions(-)
mode change 100644 => 100755 tools/testing/selftests/net/test_ingress_egress_chaining.sh
diff --git a/tools/testing/selftests/net/test_ingress_egress_chaining.sh b/tools/testing/selftests/net/test_ingress_egress_chaining.sh
old mode 100644
new mode 100755
--
2.43.0
next prev parent reply other threads:[~2024-08-24 14:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-20 20:21 [PATCH 1/1] Improve missing mods error message and make shell script executable David Hunter
2024-08-22 1:02 ` Jakub Kicinski
2024-08-23 19:08 ` David Hunter
2024-08-24 14:38 ` David Hunter [this message]
2024-08-26 16:10 ` [PATCH 1/1 V2] Selftests: net: Set executable bit for shell script patchwork-bot+netdevbpf
2024-08-26 21:40 ` Jakub Kicinski
2024-08-27 21:37 ` David Hunter
2024-08-27 21:44 ` Jakub Kicinski
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=20240824143837.228874-1-david.hunter.linux@gmail.com \
--to=david.hunter.linux@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=javier.carrasco.cruz@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.