linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Muhammad Usama Anjum <usama.anjum@collabora.com>,
	Eric Biederman <ebiederm@xmission.com>,
	Kees Cook <keescook@chromium.org>, Shuah Khan <shuah@kernel.org>,
	linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Shuah Khan <skhan@linuxfoundation.org>
Cc: kernel@collabora.com
Subject: Re: [PATCH 0/2] selftests: add ksft_exit_fail_perror()
Date: Thu, 4 Apr 2024 11:48:25 -0600	[thread overview]
Message-ID: <9a2b6f33-451b-4cb3-ad6b-be87b4c03a94@linuxfoundation.org> (raw)
In-Reply-To: <20240404161433.114497-1-usama.anjum@collabora.com>

On 4/4/24 10:14, Muhammad Usama Anjum wrote:
> In this series, ksft_exit_fail_perror() is being added which is helper
> function on top of ksft_exit_fail_msg(). It prints errno and its string
> form always. After writing and porting several kselftests, I've found
> out that most of times ksft_exit_fail_msg() isn't useful if errno value
> isn't printed. The ksft_exit_fail_perror() provides a convenient way to
> always print errno when its used.
> 
> Muhammad Usama Anjum (2):
>    selftests: add ksft_exit_fail_perror()>    selftests: exec: Use new ksft_exit_fail_perror() helper
> 
>   tools/testing/selftests/exec/recursion-depth.c | 10 +++++-----
>   tools/testing/selftests/kselftest.h            | 14 ++++++++++++++
>   2 files changed, 19 insertions(+), 5 deletions(-)
> 

Applied the two patches to linux-kselftest next for Linux 6.10-rc1.

thanks,
-- Shuah


      parent reply	other threads:[~2024-04-04 17:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-04 16:14 Muhammad Usama Anjum
2024-04-04 16:14 ` [PATCH 1/2] " Muhammad Usama Anjum
2024-04-04 16:14 ` [PATCH 2/2] selftests: exec: Use new ksft_exit_fail_perror() helper Muhammad Usama Anjum
2024-04-04 17:48 ` Shuah Khan [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=9a2b6f33-451b-4cb3-ad6b-be87b4c03a94@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=ebiederm@xmission.com \
    --cc=keescook@chromium.org \
    --cc=kernel@collabora.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=shuah@kernel.org \
    --cc=usama.anjum@collabora.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