From: patchwork-bot+netdevbpf@kernel.org
To: David Hunter <david.hunter.linux@gmail.com>
Cc: sj@kernel.org, shuah@kernel.org, allison.henderson@oracle.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, damon@lists.linux.dev, linux-mm@kvack.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
rds-devel@oss.oracle.com, javier.carrasco.cruz@gmail.com
Subject: Re: [PATCH v1 1/1] selftests: set executable bit
Date: Wed, 25 Sep 2024 05:51:29 +0000 [thread overview]
Message-ID: <172724348926.448598.2586649481930779700.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240924175500.17212-1-david.hunter.linux@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Tue, 24 Sep 2024 13:54:57 -0400 you wrote:
> Turn on the executable bit for the following script files. These scripts
> are set to TEST_PROGS in their respective Makefiles, but currently, when
> these tests are run, a warning occurs:
>
> # Warning: <file> is not executable
>
> Signed-off-by: David Hunter <david.hunter.linux@gmail.com>
>
> [...]
Here is the summary with links:
- [v1,1/1] selftests: set executable bit
https://git.kernel.org/bpf/bpf-next/c/9ea7b92b77df
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-09-25 5:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-24 17:54 David Hunter
2024-09-24 18:47 ` SeongJae Park
2024-09-25 5:51 ` patchwork-bot+netdevbpf [this message]
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=172724348926.448598.2586649481930779700.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=allison.henderson@oracle.com \
--cc=damon@lists.linux.dev \
--cc=davem@davemloft.net \
--cc=david.hunter.linux@gmail.com \
--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=linux-mm@kvack.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rds-devel@oss.oracle.com \
--cc=shuah@kernel.org \
--cc=sj@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox