linux-kselftest.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nikita Sobolev <Nikita.Sobolev@synopsys.com>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
	Shuah Khan <shuah@kernel.org>
Cc: "linux-kselftest@vger.kernel.org"
	<linux-kselftest@vger.kernel.org>,
	"linux-integrity@vger.kernel.org"
	<linux-integrity@vger.kernel.org>,
	Tadeusz Struk <tadeusz.struk@intel.com>,
	open list <linux-kernel@vger.kernel.org>,
	Peter Huewe <peterhuewe@gmx.de>, "Jason Gunthorpe" <jgg@ziepe.ca>,
	Alexey Brodkin <Alexey.Brodkin@synopsys.com>,
	"Eugeniy Paltsev" <Eugeniy.Paltsev@synopsys.com>
Subject: RE: [PATCH] selftests/tpm: Fix runtime error
Date: Sun, 10 May 2020 18:44:45 +0000	[thread overview]
Message-ID: <DM6PR12MB26848928AB4CE7B1D5BAC4B3D9A00@DM6PR12MB2684.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20200412141118.70688-1-jarkko.sakkinen@linux.intel.com>

Hi, Jarkko Sakkinen, all!

Thank you for your notes about commit and sorry for not copying the message to you!

There is definitely unwanted line of code in the commit.
After deleting that one, introduced changes work fine.

There is a hardcoded usage of /dev/tpm2 in the kernel selftest. And if there is no such device - test fails.
I believe this is not a behavior, that we expect. Test should be skipped in such case, should it?
That is what my commit makes.

So, after deleting unwanted line of code and making cosmetic changes (new description + deleting
excess newline character), can commit be submitted again?

You also mentioned reviewed-by nor tested-by tags in your message. Who should make these tags?

P.S.
Also there was a question: why do I declare exit code with a constant instead of just exit 4.
I chose this style because it is used in other kernel selftests for such kind of checks.
It is proper to follow common style rules. Should I argument this decision in commit message? 

-Nikita

> -----Original Message-----
> From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
> Sent: Sunday, April 12, 2020 5:11 PM
> To: Shuah Khan <shuah@kernel.org>
> Cc: linux-kselftest@vger.kernel.org; linux-integrity@vger.kernel.org; Jarkko
> Sakkinen <jarkko.sakkinen@linux.intel.com>; Nikita Sobolev
> <sobolev@synopsys.com>; Tadeusz Struk <tadeusz.struk@intel.com>; open
> list <linux-kernel@vger.kernel.org>
> Subject: [PATCH] selftests/tpm: Fix runtime error
> 
> There is some random clutter in test_smoke.sh:
> 
>   ./test_smoke.sh: line 3: self.flags: command not found
> 
> Remove it.
> 
> Fixes: b32694cd0724 ("Kernel selftests: tpm2: check for tpm support")
> Cc: Nikita Sobolev <Nikita.Sobolev@synopsys.com>
> Signed-off-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
> ---
> I rely on these tests and this was not even cc'd to me and obviously was
> untested. There is neither reviewed-by nor tested-by tags in the commit (not
> to mention some cosmetic things like short summary formatted wrong and the
> extra newline character).
> 
> Please do not do this next time. Thanks.
>  tools/testing/selftests/tpm2/test_smoke.sh | 2 --
>  1 file changed, 2 deletions(-)
> 
> diff --git a/tools/testing/selftests/tpm2/test_smoke.sh
> b/tools/testing/selftests/tpm2/test_smoke.sh
> index b630c7b5950a..e55d3e400666 100755
> --- a/tools/testing/selftests/tpm2/test_smoke.sh
> +++ b/tools/testing/selftests/tpm2/test_smoke.sh
> @@ -1,11 +1,9 @@
>  #!/bin/bash
>  # SPDX-License-Identifier: (GPL-2.0 OR BSD-3-Clause) -self.flags = flags
> 
>  # Kselftest framework requirement - SKIP code is 4.
>  ksft_skip=4
> 
> -
>  if [ -f /dev/tpm0 ] ; then
>  	python -m unittest -v tpm2_tests.SmokeTest
>  	python -m unittest -v tpm2_tests.AsyncTest
> --
> 2.25.1


  parent reply	other threads:[~2020-05-10 18:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-12 14:11 [PATCH] selftests/tpm: Fix runtime error Jarkko Sakkinen
2020-04-12 14:18 ` Jarkko Sakkinen
2020-05-10 18:44 ` Nikita Sobolev [this message]
2020-05-14  0:07   ` Jarkko Sakkinen

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=DM6PR12MB26848928AB4CE7B1D5BAC4B3D9A00@DM6PR12MB2684.namprd12.prod.outlook.com \
    --to=nikita.sobolev@synopsys.com \
    --cc=Alexey.Brodkin@synopsys.com \
    --cc=Eugeniy.Paltsev@synopsys.com \
    --cc=jarkko.sakkinen@linux.intel.com \
    --cc=jgg@ziepe.ca \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=peterhuewe@gmx.de \
    --cc=shuah@kernel.org \
    --cc=tadeusz.struk@intel.com \
    /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).