linux-kselftest.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: Kees Cook <keescook@chromium.org>
Cc: Shuah Khan <shuah@kernel.org>,
	"Tobin C. Harding" <tobin@kernel.org>,
	"open list:KERNEL SELFTEST FRAMEWORK" 
	<linux-kselftest@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>,
	lkft-triage@lists.linaro.org,
	Anders Roxell <anders.roxell@linaro.org>
Subject: Re: [PATCH] selftests: Move kselftest_module.sh into kselftest/
Date: Tue, 12 Nov 2019 12:57:27 +0530	[thread overview]
Message-ID: <CA+G9fYvcD=rNmkQn_bsBO0RUVwhQA=TtzP1AeqLqwfKjorLWXg@mail.gmail.com> (raw)
In-Reply-To: <201910301244.9C3CABCA0@keescook>

Hi Kees,

Thanks for the fix patch.

On Thu, 31 Oct 2019 at 01:15, Kees Cook <keescook@chromium.org> wrote:
>
> The kselftest_module.sh file was not being installed by the Makefile
> "install" target, rendering the lib/*.sh tests nonfunction. This fixes
> that and takes the opportunity to move it into the kselftest/ subdirectory
> which is where the kselftest infrastructure bits are collecting.
>
> Reported-by: Naresh Kamboju <naresh.kamboju@linaro.org>
> Link: https://lore.kernel.org/lkml/CA+G9fYsfJpXQvOvHdjtg8z4a89dSStOQZOKa9zMjjQgWKng1aw@mail.gmail.com
> Fixes: d3460527706e ("kselftest: Add test runner creation script")
> Signed-off-by: Kees Cook <keescook@chromium.org>

Now this patch merged into linux next tree.
Following tests getting pass.
 kselftest:
    * lib/bitmap.sh
    * lib/printf.sh
    * lib/strscpy.sh

Thank you.

Best regards
Naresh Kamboju

      reply	other threads:[~2019-11-12  7:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-30 19:45 [PATCH] selftests: Move kselftest_module.sh into kselftest/ Kees Cook
2019-11-12  7:27 ` Naresh Kamboju [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='CA+G9fYvcD=rNmkQn_bsBO0RUVwhQA=TtzP1AeqLqwfKjorLWXg@mail.gmail.com' \
    --to=naresh.kamboju@linaro.org \
    --cc=anders.roxell@linaro.org \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=shuah@kernel.org \
    --cc=tobin@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;
as well as URLs for NNTP newsgroup(s).