The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Daniel Palmer <daniel@0x0f.com>
Cc: linux@weissschuh.net, linux-m68k@vger.kernel.org,
	geert@linux-m68k.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tools/nolibc: Add m68k support
Date: Sat, 26 Apr 2025 08:56:13 +0200	[thread overview]
Message-ID: <20250426065613.GA8661@1wt.eu> (raw)
In-Reply-To: <CAFr9PXkU3W6DdYKhHz13K7bk9bnik67R85wqYUwHeROKEx59zA@mail.gmail.com>

On Sat, Apr 26, 2025 at 03:16:35PM +0900, Daniel Palmer wrote:
> Hi Willy,
> 
> On Sat, 26 Apr 2025 at 14:14, Willy Tarreau <w@1wt.eu> wrote:
> > Nice, thank you! Could you please also add support for it to
> > tools/testing/selftests/nolibc/ and verify that it works ?
> 
> Sure, doing that now. For now it'll be using the mmu enabled m68k virt
> machine that QEMU supports out of the box.

Ah, I didn't know that there's both mmu and nommu for m68k :-)

> > changes. You may possible have to add a few ifndef, as I don't
> > think we've ever had a nommu platform yet. If you face too many
> > failures or just difficulties, please let us know so that we can
> > figure together a suitable solution.
> 
> I need to test actually building and running something for nommu but I
> will do that later today.
> Making nommu test automatically might be a bit difficult though as I
> think it only really works with some changes I have to linux and QEMU.

OK no worries, my point really is that it's important to implement the
test for the target platform. If it's mmu only that's fine, as it will
ensure we don't break it in future updates.

thanks,
Willy

  reply	other threads:[~2025-04-26  6:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-26  4:12 [PATCH] tools/nolibc: Add m68k support Daniel Palmer
2025-04-26  5:14 ` Willy Tarreau
2025-04-26  6:16   ` Daniel Palmer
2025-04-26  6:56     ` Willy Tarreau [this message]
2025-04-26 13:09       ` Daniel Palmer
2025-04-26 12:37     ` Greg Ungerer
2025-04-26 13:06       ` Daniel Palmer
2025-04-26 13:57         ` Greg Ungerer

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=20250426065613.GA8661@1wt.eu \
    --to=w@1wt.eu \
    --cc=daniel@0x0f.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=linux@weissschuh.net \
    /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