mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vincenzo Frascino <vincenzo.frascino@arm.com>
To: Shuah Khan <skhan@linuxfoundation.org>,
	Cristian Marussi <cristian.marussi@arm.com>
Cc: linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
	Shuah Khan <shuah@kernel.org>, Andy Lutomirski <luto@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH v3] kselftest: Fix vdso_test_abi return status
Date: Mon, 31 Jan 2022 11:44:01 +0000	[thread overview]
Message-ID: <f1bbd32d-470c-d5ea-f324-85189e00f5e6@arm.com> (raw)
In-Reply-To: <25eb270c-fa11-f2bc-0686-b5a8c55cd0a7@linuxfoundation.org>

Hi Shuah,

On 1/28/22 5:41 PM, Shuah Khan wrote:
> On 1/28/22 10:35 AM, Shuah Khan wrote:
>> On 1/28/22 7:44 AM, Cristian Marussi wrote:
>>> On Fri, Jan 28, 2022 at 01:07:01PM +0000, Vincenzo Frascino wrote:
>>>> vdso_test_abi contains a batch of tests that verify the validity of the
>>>> vDSO ABI.
>>>>
>>>> When a vDSO symbol is not found the relevant test is skipped reporting
>>>> KSFT_SKIP. All the tests return values are then added in a single
>>>> variable which is checked to verify failures. This approach can have
>>>> side effects which result in reporting the wrong kselftest exit status.
>>>>
>>>> Fix vdso_test_abi verifying the return code of each test separately.
>>>>
>>>> Cc: Shuah Khan <shuah@kernel.org>
>>>> Cc: Andy Lutomirski <luto@kernel.org>
>>>> Cc: Thomas Gleixner <tglx@linutronix.de>
>>>> Reported-by: Cristian Marussi <cristian.marussi@arm.com>
>>>> Signed-off-by: Vincenzo Frascino <vincenzo.frascino@arm.com>
>>>> ---
>>>
>>> Hi,
>>>
>>> LGTM.
>>>
>>> Tested-by: Cristian Marussi <cristian.marussi@arm.com>
>>>
>>> Thanks,
>>> Cristian
>>
>> Thank you both. Will queue this up for 5.17 rc3.
>>
> 
> Vincenzo,
> 
> A couple of checkpatch warns. Please fix them and send me v4.
> 

It should be sorted now, I just posted v4. Please let me know if anything else
is required from my side.

Thanks!

--->8---

$ scripts/checkpatch.pl v4-0001-kselftest-Fix-vdso_test_abi-return-status.patch
total: 0 errors, 0 warnings, 252 lines checked


> thanks,
> -- Shuah

-- 
Regards,
Vincenzo

      reply	other threads:[~2022-01-31 11:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-28 13:07 Vincenzo Frascino
2022-01-28 14:44 ` Cristian Marussi
2022-01-28 17:35   ` Shuah Khan
2022-01-28 17:41     ` Shuah Khan
2022-01-31 11:44       ` Vincenzo Frascino [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=f1bbd32d-470c-d5ea-f324-85189e00f5e6@arm.com \
    --to=vincenzo.frascino@arm.com \
    --cc=cristian.marussi@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=shuah@kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=tglx@linutronix.de \
    /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®