From: Andreas Schwab <schwab@linux-m68k.org>
To: Helge Deller <deller@gmx.de>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Helge Deller <deller@kernel.org>,
qemu-devel@nongnu.org
Subject: Re: [PATCH] linux-user: Fix msqid_ds struct wrt 32-bit big endian architectures
Date: Fri, 07 Aug 2026 19:03:35 +0200 [thread overview]
Message-ID: <87bjbdhnh4.fsf@igel.home> (raw)
In-Reply-To: <090faa9e-0ba2-4620-8d27-8fa4b7ac17af@gmx.de>
On Aug 07 2026, Helge Deller wrote:
> Andreas, do you agree as well, that all 32-bit kernel architectures
> should follow this path and we should drop the "preferred" thing and switch
> to a native 64-bit time value?
That would be an ABI break. But on the glibc side, the m68k definition
of struct msqid_ds is broken as well, having incompatible layout beteen
_TIME_BITS=64 and _TIME_BITS=32 definitions.
> If so, I'd willing to come up with a kernel patch...
Let's see what the kernel experts recommend.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
prev parent reply other threads:[~2026-08-07 17:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 19:29 [PATCH] linux-user: Fix msqid_ds struct wrt 32-bit big endian architectures Helge Deller
2026-07-31 18:05 ` Peter Maydell
2026-07-31 19:36 ` Helge Deller
2026-08-01 12:11 ` Peter Maydell
2026-08-01 20:58 ` Helge Deller
2026-08-01 21:38 ` Helge Deller
2026-08-03 11:53 ` Geert Uytterhoeven
2026-08-03 17:47 ` Andreas Schwab
2026-08-03 18:08 ` Andreas Schwab
2026-08-03 21:01 ` Helge Deller
2026-08-03 21:42 ` Andreas Schwab
2026-08-04 6:30 ` Helge Deller
2026-08-07 13:12 ` Peter Maydell
2026-08-07 15:08 ` Helge Deller
2026-08-07 17:03 ` Andreas Schwab [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=87bjbdhnh4.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=deller@gmx.de \
--cc=deller@kernel.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/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.