From: Atul Kumar Pant <atulpant.linux@gmail.com>
To: a.zummo@towertech.it, alexandre.belloni@bootlin.com
Cc: shuah@kernel.org, linux-kernel-mentees@lists.linuxfoundation.org,
linux-rtc@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6] selftests: rtc: Fixes rtctest error handling.
Date: Sat, 23 Sep 2023 23:06:52 +0530 [thread overview]
Message-ID: <20230923173652.GC159038@atom0118> (raw)
In-Reply-To: <20230817091401.72674-1-atulpant.linux@gmail.com>
On Thu, Aug 17, 2023 at 02:44:01PM +0530, Atul Kumar Pant wrote:
> Adds a check to verify if the rtc device file is valid or not
> and prints a useful error message if the file is not accessible.
>
> Signed-off-by: Atul Kumar Pant <atulpant.linux@gmail.com>
> ---
>
> changes since v5:
> Updated error message to use strerror().
> If the rtc file is invalid, the skip the test.
>
> changes since v4:
> Updated the commit message.
>
> changes since v3:
> Added Linux-kselftest and Linux-kernel mailing lists.
>
> changes since v2:
> Changed error message when rtc file does not exist.
>
> changes since v1:
> Removed check for uid=0
> If rtc file is invalid, then exit the test.
>
> tools/testing/selftests/rtc/rtctest.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/tools/testing/selftests/rtc/rtctest.c b/tools/testing/selftests/rtc/rtctest.c
> index 630fef735c7e..27b466111885 100644
> --- a/tools/testing/selftests/rtc/rtctest.c
> +++ b/tools/testing/selftests/rtc/rtctest.c
> @@ -15,6 +15,7 @@
> #include <sys/types.h>
> #include <time.h>
> #include <unistd.h>
> +#include <error.h>
>
> #include "../kselftest_harness.h"
> #include "../kselftest.h"
> @@ -437,7 +438,7 @@ int main(int argc, char **argv)
> if (access(rtc_file, F_OK) == 0)
> ret = test_harness_run(argc, argv);
> else
> - ksft_exit_fail_msg("[ERROR]: Cannot access rtc file %s - Exiting\n", rtc_file);
> + ksft_exit_skip("%s: %s\n", rtc_file, strerror(errno));
>
> return ret;
> }
> --
> 2.25.1
>
Hi Shuah, I have made the changes as per your comments. Can you please
review the changes ?
next prev parent reply other threads:[~2023-09-23 17:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 9:14 [PATCH v6] selftests: rtc: Fixes rtctest error handling Atul Kumar Pant
2023-09-23 17:36 ` Atul Kumar Pant [this message]
2023-10-07 15:43 ` Atul Kumar Pant
2023-11-07 21:27 ` Shuah Khan
2023-11-12 13:49 ` Atul Kumar Pant
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=20230923173652.GC159038@atom0118 \
--to=atulpant.linux@gmail.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).