All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: Shuah Khan <shuah@kernel.org>,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
	Sven Schnelle <svens@linux.ibm.com>
Subject: Re: [PATCH 0/2] tools/nolibc: support for 32-bit s390
Date: Sat, 1 Feb 2025 11:19:31 +0100	[thread overview]
Message-ID: <20250201101931.GF5849@1wt.eu> (raw)
In-Reply-To: <20250122-nolibc-s390-v1-0-8c765f00e871@weissschuh.net>

On Wed, Jan 22, 2025 at 07:43:44PM +0100, Thomas Weißschuh wrote:
> Support for 32-bit s390 is very easy to implement and useful for
> testing. For example I used to test some generic compat_ptr() logic,
> which is only testable on 32-bit s390.
> 
> The series depends on my other series
> "selftests/nolibc: test kernel configuration cleanups".
> (It's not a hard dependency, only a minor diff conflict)
> 
> Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>

I'm generally fine with the series from the nolibc perspective. I've
added Sven in Cc in case he wants to double-check anything, given that
he initially contributed the s390 support.

Acked-by: Willy Tarreau <w@1wt.eu>

Thanks!
Willy

      parent reply	other threads:[~2025-02-01 10:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-22 18:43 [PATCH 0/2] tools/nolibc: support for 32-bit s390 Thomas Weißschuh
2025-01-22 18:43 ` [PATCH 1/2] selftests/nolibc: rename s390 to s390x Thomas Weißschuh
2025-01-22 18:43 ` [PATCH 2/2] tools/nolibc: add support for 32-bit s390 Thomas Weißschuh
2025-02-05  8:00   ` Sven Schnelle
2025-02-01 10:19 ` 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=20250201101931.GF5849@1wt.eu \
    --to=w@1wt.eu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux@weissschuh.net \
    --cc=shuah@kernel.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.