From: Petr Mladek <pmladek@suse.com>
To: Miroslav Benes <mbenes@suse.cz>
Cc: shuah <shuah@kernel.org>,
jpoimboe@redhat.com, jikos@kernel.org, joe.lawrence@redhat.com,
live-patching@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests: livepatch use TEST_PROGS for test shell scripts
Date: Mon, 15 Apr 2019 14:42:55 +0200 [thread overview]
Message-ID: <20190415124255.hcraeeiu5xoziber@pathway.suse.cz> (raw)
In-Reply-To: <alpine.LSU.2.21.1904121535100.773@pobox.suse.cz>
On Fri 2019-04-12 15:37:37, Miroslav Benes wrote:
> From: Miroslav Benes <mbenes@suse.cz>
> Date: Fri, 12 Apr 2019 15:31:42 +0200
> Subject: [PATCH] selftests/livepatch: Add functions.sh to TEST_PROGS_EXTENDED
>
> Add functions.sh to TEST_PROGS_EXTENDED so that it is installed along
> with the rest of the selftests and they can be run.
>
> Originally-by: Shuah Khan <shuah@kernel.org>
> Signed-off-by: Miroslav Benes <mbenes@suse.cz>
> ---
> tools/testing/selftests/livepatch/Makefile | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tools/testing/selftests/livepatch/Makefile b/tools/testing/selftests/livepatch/Makefile
> index 114f43e2081a..fd405402c3ff 100644
> --- a/tools/testing/selftests/livepatch/Makefile
> +++ b/tools/testing/selftests/livepatch/Makefile
> @@ -1,5 +1,6 @@
> # SPDX-License-Identifier: GPL-2.0
>
> +TEST_PROGS_EXTENDED := functions.sh
> TEST_PROGS := \
> test-livepatch.sh \
> test-callbacks.sh \
> --
> 2.21.0
The patch has been committed into the branch for-5.1/upstream-fixes.
Best Regards,
Petr
prev parent reply other threads:[~2019-04-15 12:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-12 1:18 Shuah Khan
2019-04-12 7:03 ` Miroslav Benes
2019-04-12 13:26 ` shuah
2019-04-12 13:37 ` Miroslav Benes
2019-04-12 17:05 ` shuah
2019-04-12 18:51 ` Joe Lawrence
2019-04-12 19:06 ` shuah
2019-04-15 12:42 ` Petr Mladek [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=20190415124255.hcraeeiu5xoziber@pathway.suse.cz \
--to=pmladek@suse.com \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®