From: Willy Tarreau <w@1wt.eu>
To: Sven Schnelle <svens@linux.ibm.com>
Cc: "Paul E . McKenney" <paulmck@kernel.org>,
Josh Triplett <josh@joshtriplett.org>,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Lai Jiangshan <jiangshanlai@gmail.com>,
linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org
Subject: Re: [PATCH v3 0/5] add s390 support to nolibc and rcutorture
Date: Sun, 8 Jan 2023 10:20:48 +0100 [thread overview]
Message-ID: <20230108092048.GA17754@1wt.eu> (raw)
In-Reply-To: <20230103071957.222360-1-svens@linux.ibm.com>
Hi Sven,
On Tue, Jan 03, 2023 at 08:19:52AM +0100, Sven Schnelle wrote:
> Hi,
>
> these patches add support for the s390 architecture both to nolibc
> and rcutorture. Note that this only adds support for the 64 bit
> version, no support for 31 bit (compat) is added. For nolibc it
> includes one bugfix to make the fd_set datatype match the kernel
> type.
Perfect, looks clean and works out of the box now. I've queued the
fd_set one for fixes and will submit the rest to Paul for his dev
branch. Thank you!
Willy
prev parent reply other threads:[~2023-01-08 9:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 7:19 [PATCH v3 0/5] add s390 support to nolibc and rcutorture Sven Schnelle
2023-01-03 7:19 ` [PATCH v3 1/5] nolibc: fix fd_set type Sven Schnelle
2023-01-03 7:19 ` [PATCH v3 2/5] nolibc: add support for s390 Sven Schnelle
2023-01-03 7:19 ` [PATCH v3 3/5] selftests/nolibc: add s390 support Sven Schnelle
2023-01-03 19:03 ` Heiko Carstens
2023-01-03 7:19 ` [PATCH v3 4/5] rcutorture: add support for s390 Sven Schnelle
2023-01-03 7:19 ` [PATCH v3 5/5] rcutorture: build initrd for rcutorture with nolibc Sven Schnelle
2023-01-08 9:20 ` Willy Tarreau [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=20230108092048.GA17754@1wt.eu \
--to=w@1wt.eu \
--cc=jiangshanlai@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=paulmck@kernel.org \
--cc=rostedt@goodmis.org \
--cc=svens@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.