public inbox for linux-kselftest@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Shuah Khan <skhan@linuxfoundation.org>
Cc: davem@davemloft.net, kuba@kernel.org, shuah@kernel.org,
	netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests: net: af_unix: Fix makefile to use TEST_GEN_PROGS
Date: Sun, 19 Sep 2021 12:30:07 +0000	[thread overview]
Message-ID: <163205460747.12471.18162549656003560869.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210917215356.33791-1-skhan@linuxfoundation.org>

Hello:

This patch was applied to netdev/net.git (refs/heads/master):

On Fri, 17 Sep 2021 15:53:56 -0600 you wrote:
> Makefile uses TEST_PROGS instead of TEST_GEN_PROGS to define
> executables. TEST_PROGS is for shell scripts that need to be
> installed and run by the common lib.mk framework. The common
> framework doesn't touch TEST_PROGS when it does build and clean.
> 
> As a result "make kselftest-clean" and "make clean" fail to remove
> executables. Run and install work because the common framework runs
> and installs TEST_PROGS. Build works because the Makefile defines
> "all" rule which is unnecessary if TEST_GEN_PROGS is used.
> 
> [...]

Here is the summary with links:
  - selftests: net: af_unix: Fix makefile to use TEST_GEN_PROGS
    https://git.kernel.org/netdev/net/c/e30cd812dffa

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2021-09-19 12:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-17 21:53 [PATCH] selftests: net: af_unix: Fix makefile to use TEST_GEN_PROGS Shuah Khan
2021-09-19 12:30 ` 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=163205460747.12471.18162549656003560869.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=skhan@linuxfoundation.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