From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Louis Taylor <louis@kragniz.eu>
Cc: Willy Tarreau <w@1wt.eu>, Shuah Khan <shuah@kernel.org>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 5/5] tools/nolibc: mark more test functions as static
Date: Thu, 6 Mar 2025 18:00:17 +0100 [thread overview]
Message-ID: <61636d83-8154-4e7b-850b-1c4ed9a2c2f2@t-8ch.de> (raw)
In-Reply-To: <20250304075846.66563-5-louis@kragniz.eu>
On 2025-03-04 07:58:19+0000, Louis Taylor wrote:
> It was mentioned that a new test_ function should be static, so go back
> over existing functions and mark those static as well.
Actually Willy wants these non-static for debugging purposes.
I can't seem to get that into my head -.-
Let's drop this one.
> Signed-off-by: Louis Taylor <louis@kragniz.eu>
> ---
> tools/testing/selftests/nolibc/nolibc-test.c | 14 +++++++-------
> 1 file changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/tools/testing/selftests/nolibc/nolibc-test.c b/tools/testing/selftests/nolibc/nolibc-test.c
> index 2a1629938dd6..b5464ca8d050 100644
> --- a/tools/testing/selftests/nolibc/nolibc-test.c
> +++ b/tools/testing/selftests/nolibc/nolibc-test.c
> @@ -807,7 +807,7 @@ static int test_dirent(void)
> return 0;
> }
>
> -int test_getpagesize(void)
> +static int test_getpagesize(void)
> {
> int x = getpagesize();
> int c;
> @@ -836,7 +836,7 @@ int test_getpagesize(void)
> return !c;
> }
>
> -int test_fork(void)
> +static int test_fork(void)
> {
> int status;
> pid_t pid;
> @@ -861,7 +861,7 @@ int test_fork(void)
> }
> }
>
> -int test_stat_timestamps(void)
> +static int test_stat_timestamps(void)
> {
> struct stat st;
>
> @@ -883,7 +883,7 @@ int test_stat_timestamps(void)
> return 0;
> }
>
> -int test_uname(void)
> +static int test_uname(void)
> {
> struct utsname buf;
> char osrelease[sizeof(buf.release)];
> @@ -922,7 +922,7 @@ int test_uname(void)
> return 0;
> }
>
> -int test_mmap_munmap(void)
> +static int test_mmap_munmap(void)
> {
> int ret, fd, i, page_size;
> void *mem;
> @@ -980,7 +980,7 @@ int test_mmap_munmap(void)
> return !!ret;
> }
>
> -int test_pipe(void)
> +static int test_pipe(void)
> {
> const char *const msg = "hello, nolibc";
> int pipefd[2];
> @@ -1001,7 +1001,7 @@ int test_pipe(void)
> return !!memcmp(buf, msg, len);
> }
>
> -int test_rlimit(void)
> +static int test_rlimit(void)
> {
> struct rlimit rlim = {
> .rlim_cur = 1 << 20,
> --
> 2.45.2
>
next prev parent reply other threads:[~2025-03-06 17:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 7:58 [PATCH v2 1/5] tools/nolibc: add support for openat(2) Louis Taylor
2025-03-04 7:58 ` [PATCH v2 2/5] tools/nolibc: always use openat(2) instead of open(2) Louis Taylor
2025-03-06 16:56 ` Thomas Weißschuh
2025-03-04 7:58 ` [PATCH v2 3/5] tools/nolibc: process open() vararg as mode_t Louis Taylor
2025-03-06 16:56 ` Thomas Weißschuh
2025-03-04 7:58 ` [PATCH v2 4/5] tools/nolibc: drop outdated example from overview comment Louis Taylor
2025-03-06 16:58 ` Thomas Weißschuh
2025-03-04 7:58 ` [PATCH v2 5/5] tools/nolibc: mark more test functions as static Louis Taylor
2025-03-06 17:00 ` Thomas Weißschuh [this message]
2025-03-06 17:06 ` Willy Tarreau
2025-03-04 8:11 ` [PATCH v2 1/5] tools/nolibc: add support for openat(2) Willy Tarreau
2025-03-06 17:22 ` Thomas Weißschuh
2025-03-06 17:42 ` Willy Tarreau
2025-03-06 17:10 ` Thomas Weißschuh
2025-03-06 18:30 ` Louis Taylor
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=61636d83-8154-4e7b-850b-1c4ed9a2c2f2@t-8ch.de \
--to=linux@weissschuh.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=louis@kragniz.eu \
--cc=shuah@kernel.org \
--cc=w@1wt.eu \
/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®