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 v2 0/5] add s390 support to nolibc and rcutorture
Date: Mon, 2 Jan 2023 15:33:02 +0100 [thread overview]
Message-ID: <20230102143302.GF29287@1wt.eu> (raw)
In-Reply-To: <yt9d358trpcx.fsf@linux.ibm.com>
On Mon, Jan 02, 2023 at 03:19:10PM +0100, Sven Schnelle wrote:
> Willy Tarreau <w@1wt.eu> writes:
>
> > On Mon, Jan 02, 2023 at 11:51:07AM +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.
> >>
> >> Changes in v2:
> >>
> >> - use __attribute__((unused)) instead of __maybe_unused
> >> - prefer aghi over lay, as lay is not present in all architecure levels
> >> - add -m64 CFLAG to force 64 bit mode for compiler that can do 31bit and 64bit mode
> >
> > Excellent, now works out of the box for me, thank you Sven!.
> >
> > Paul, would you mind taking these ones for your dev branch instead
> > of the previous ones ?
>
> Hrm, while looking at the code to make the adjustments for the auxv
> stuff, i noted that the envp handling in the startup code is wrong. So i
> have to fix that and send a v3 of the patchset.
OK thank you for letting us know!
Willy
prev parent reply other threads:[~2023-01-02 14:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-02 10:51 [PATCH v2 0/5] add s390 support to nolibc and rcutorture Sven Schnelle
2023-01-02 10:51 ` [PATCH v2 1/5] nolibc: fix fd_set type Sven Schnelle
2023-01-02 10:51 ` [PATCH v2 2/5] nolibc: add support for s390 Sven Schnelle
2023-01-02 10:51 ` [PATCH v2 3/5] selftests/nolibc: add s390 support Sven Schnelle
2023-01-02 10:51 ` [PATCH v2 4/5] rcutorture: add support for s390 Sven Schnelle
2023-01-02 10:51 ` [PATCH v2 5/5] rcutorture: build initrd for rcutorture with nolibc Sven Schnelle
2023-01-02 11:02 ` [PATCH v2 0/5] add s390 support to nolibc and rcutorture Willy Tarreau
2023-01-02 14:19 ` Sven Schnelle
2023-01-02 14:33 ` 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=20230102143302.GF29287@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox