public inbox for [email protected]
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <[email protected]>
To: Greg Ungerer <[email protected]>
Cc: Guenter Roeck <[email protected]>,
	"Christoph Lameter (Ampere)" <[email protected]>,
	Vlastimil Babka <[email protected]>,
	 Pekka Enberg <[email protected]>,
	David Rientjes <[email protected]>,
	 Joonsoo Kim <[email protected]>,
	Andrew Morton <[email protected]>,
	 Roman Gushchin <[email protected]>,
	Hyeonggon Yoo <[email protected]>,
	 Jens Axboe <[email protected]>,
	Pavel Begunkov <[email protected]>,
	 Mike Rapoport <[email protected]>,
	Christian Brauner <[email protected]>,
	Kees Cook <[email protected]>,  Jann Horn <[email protected]>,
	[email protected], [email protected],
	 [email protected], [email protected]
Subject: Re: [PATCH] slab: Fix too strict alignment check in create_cache()
Date: Fri, 22 Nov 2024 09:12:55 +0100	[thread overview]
Message-ID: <CAMuHMdX-wGB6QvYpUb+Qur85pnScyxo_aaQFxe6BSOEg+Eeogg@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>

On Fri, Nov 22, 2024 at 1:23 AM Greg Ungerer <[email protected]> wrote:
> On 22/11/24 04:30, Guenter Roeck wrote:
> > Do we really need to continue supporting nommu machines ? Is anyone
> > but me even boot testing those ?
>
> Yes. Across many architectures. And yes on every release, and for m68k building
> and testing on every rc for nommu at a minimum.
>
> I rarely hit build or testing problems on nonmmu targets. At least every kernel
> release I build and test armnommu (including thumb2 on cortex), m68k, RISC-V and
> xtensa. They are all easy, qemu targets for them all. Thats just me. So I would
> guess there are others building and testing too.

FTR, I do regular boot tests on K210 (SiPEED MAiX BiT RISC-V nommu).
Getting harder, as 8 MiB of RAM is not much...

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  reply	other threads:[~2024-11-22  8:13 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-20 12:46 [PATCH] slab: Fix too strict alignment check in create_cache() Geert Uytterhoeven
2024-11-20 12:49 ` Geert Uytterhoeven
2024-11-20 15:00 ` Guenter Roeck
2024-11-20 15:01 ` Jens Axboe
2024-11-20 15:03 ` Vlastimil Babka
2024-11-20 15:14   ` Guenter Roeck
2024-11-20 15:44     ` Vlastimil Babka
2024-11-20 15:50       ` Geert Uytterhoeven
2024-11-20 17:50   ` Christoph Lameter (Ampere)
2024-11-21  3:51     ` Matthew Wilcox
2024-11-21  8:15     ` Geert Uytterhoeven
2024-11-21 17:23       ` Christoph Lameter (Ampere)
2024-11-21 18:30         ` Guenter Roeck
2024-11-21 18:35           ` Jens Axboe
2024-11-21 18:50           ` Geert Uytterhoeven
2024-11-21 19:08             ` Guenter Roeck
2024-11-21 19:22               ` Guenter Roeck
2024-11-22  9:45                 ` Lorenzo Stoakes
2024-11-22 12:55                   ` Lorenzo Stoakes
2024-11-22  0:23           ` Greg Ungerer
2024-11-22  8:12             ` Geert Uytterhoeven [this message]
2024-11-22  8:25           ` Max Filippov
2024-11-21 10:19 ` Christian Brauner
2024-11-21 22:02 ` John Paul Adrian Glaubitz
2024-11-22  2:12   ` Finn Thain
2024-11-22  7:55     ` Geert Uytterhoeven

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=CAMuHMdX-wGB6QvYpUb+Qur85pnScyxo_aaQFxe6BSOEg+Eeogg@mail.gmail.com \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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