mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Thomas Weißschuh" <linux@weissschuh.net>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Shuah Khan <skhan@linuxfoundation.org>, Willy Tarreau <w@1wt.eu>,
	 linux-kernel@vger.kernel.org
Subject: [GIT PULL] nolibc changes for v6.13
Date: Fri, 1 Nov 2024 14:22:13 +0000	[thread overview]
Message-ID: <7bac1319-fe1c-454d-b96d-8344bdce3961@t-8ch.de> (raw)
In-Reply-To: <ba23217d-5eaf-4146-8ed7-27289cece364@t-8ch.de>

(resend to add missing Cc: LKML)


Hi Paul,

The following changes since commit 9852d85ec9d492ebef56dc5f229416c925758edc:

  Linux 6.12-rc1 (2024-09-29 15:06:19 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/nolibc/linux-nolibc.git tags/nolibc-20241101-for-6.13-1

for you to fetch changes up to ad0558f3883130954ca724697f2d19aef93967b3:

  selftests/nolibc: start qemu with 1 GiB of memory (2024-10-07 21:57:45 +0200)

----------------------------------------------------------------
nolibc changes for 6.13

Changes
-------

* Fix potential error due to missing #include on s390
* Compatibility with -Wmissing-fallthrough
* Run qemu with more memory during tests

----------------------------------------------------------------
Thomas Weißschuh (3):
      tools/nolibc: s390: include std.h
      tools/nolibc: compiler: add macro __nolibc_fallthrough
      selftests/nolibc: start qemu with 1 GiB of memory

 tools/include/nolibc/arch-s390.h        | 1 +
 tools/include/nolibc/compiler.h         | 6 ++++++
 tools/include/nolibc/stdio.h            | 3 ++-
 tools/testing/selftests/nolibc/Makefile | 4 ++--
 4 files changed, 11 insertions(+), 3 deletions(-)

Test report:

$ ./run-tests.sh
i386:          195 test(s): 195 passed,   0 skipped,   0 failed => status: success
x86_64:        195 test(s): 195 passed,   0 skipped,   0 failed => status: success
arm64:         195 test(s): 195 passed,   0 skipped,   0 failed => status: success
arm:           195 test(s): 195 passed,   0 skipped,   0 failed => status: success
mips32le:      195 test(s): 194 passed,   1 skipped,   0 failed => status: warning
mips32be:      195 test(s): 194 passed,   1 skipped,   0 failed => status: warning
ppc:           195 test(s): 195 passed,   0 skipped,   0 failed => status: success
ppc64:         195 test(s): 195 passed,   0 skipped,   0 failed => status: success
ppc64le:       195 test(s): 195 passed,   0 skipped,   0 failed => status: success
riscv:         195 test(s): 195 passed,   0 skipped,   0 failed => status: success
s390:          195 test(s): 194 passed,   1 skipped,   0 failed => status: warning
loongarch:     195 test(s): 194 passed,   1 skipped,   0 failed => status: warning

$ ./run-tests.sh -m user
i386:          195 test(s): 193 passed,   2 skipped,   0 failed => status: warning
x86_64:        195 test(s): 193 passed,   2 skipped,   0 failed => status: warning
arm64:         195 test(s): 193 passed,   2 skipped,   0 failed => status: warning
arm:           195 test(s): 193 passed,   2 skipped,   0 failed => status: warning
mips32le:      195 test(s): 192 passed,   3 skipped,   0 failed => status: warning
mips32be:      195 test(s): 192 passed,   3 skipped,   0 failed => status: warning
ppc:           195 test(s): 193 passed,   2 skipped,   0 failed => status: warning
ppc64:         195 test(s): 193 passed,   2 skipped,   0 failed => status: warning
ppc64le:       195 test(s): 193 passed,   2 skipped,   0 failed => status: warning
riscv:         195 test(s): 193 passed,   2 skipped,   0 failed => status: warning
s390:          195 test(s): 192 passed,   3 skipped,   0 failed => status: warning
loongarch:     195 test(s): 192 passed,   3 skipped,   0 failed => status: warning

$ ./run-tests.sh -m user -l
i386:          195 test(s): 193 passed,   2 skipped,   0 failed => status: warning
x86_64:        195 test(s): 193 passed,   2 skipped,   0 failed => status: warning
arm64:         195 test(s): 193 passed,   2 skipped,   0 failed => status: warning
arm:           195 test(s): 193 passed,   2 skipped,   0 failed => status: warning
mips32le:      195 test(s): 192 passed,   3 skipped,   0 failed => status: warning
mips32be:      195 test(s): 192 passed,   3 skipped,   0 failed => status: warning
ppc:           195 test(s): 192 passed,   3 skipped,   0 failed => status: warning
ppc64:         195 test(s): 192 passed,   3 skipped,   0 failed => status: warning
ppc64le:       195 test(s): 192 passed,   3 skipped,   0 failed => status: warning
riscv:         195 test(s): 192 passed,   3 skipped,   0 failed => status: warning
s390:          195 test(s): 192 passed,   3 skipped,   0 failed => status: warning
loongarch:     195 test(s): 192 passed,   3 skipped,   0 failed => status: warning


Thanks,
Thomas

       reply	other threads:[~2024-11-01 14:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ba23217d-5eaf-4146-8ed7-27289cece364@t-8ch.de>
2024-11-01 14:22 ` Thomas Weißschuh [this message]
2024-11-01 20:22   ` Paul E. McKenney
2024-11-01 21:23     ` Thomas Weißschuh
2024-11-01 21:33       ` Willy Tarreau
2024-11-01 21:40         ` Thomas Weißschuh
2024-11-01 22:01           ` Willy Tarreau
2024-11-01 22:04       ` Paul E. McKenney
2024-11-17 18:40 Paul E. McKenney
2024-11-19 19:06 ` pr-tracker-bot

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=7bac1319-fe1c-454d-b96d-8344bdce3961@t-8ch.de \
    --to=linux@weissschuh.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@kernel.org \
    --cc=skhan@linuxfoundation.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®