From: "Arnd Bergmann" <arnd@arndb.de>
To: "Sam Ravnborg" <sam@ravnborg.org>,
"Andreas Larsson" <andreas@gaisler.com>,
"David S . Miller" <davem@davemloft.net>,
sparclinux@vger.kernel.org
Cc: "Nick Bowler" <nbowler@draconx.ca>,
linux-kernel@vger.kernel.org,
"Atish Patra" <atish.patra@oracle.com>,
stable@vger.kernel.org, "Bob Picco" <bob.picco@oracle.com>,
"Vijay Kumar" <vijay.ac.kumar@oracle.com>
Subject: Re: [PATCH 00/10] sparc64: Fix CPU online bug and warning fixes
Date: Sat, 30 Mar 2024 11:19:37 +0100 [thread overview]
Message-ID: <4e57929b-1539-4a25-ab05-a2a9e04ecc1d@app.fastmail.com> (raw)
In-Reply-To: <20240330-sparc64-warnings-v1-0-37201023ee2f@ravnborg.org>
On Sat, Mar 30, 2024, at 10:57, Sam Ravnborg via B4 Relay wrote:
> Nick Bowler reported that sparc64 failed to bring all his CPU's online,
> and that turned out to be an easy fix.
>
> The sparc64 build was rather noisy with a lot of warnings which had
> irritated me enough to go ahead and fix them.
> With this set of patches my arch/sparc/ is almost warning free for
> all{no,yes,mod}config + defconfig builds.
Patches 1-9 look good to me,
Acked-by: Arnd Bergmann <arnd@arndb.de>
> There is one warning about "clone3 not implemented", which I have ignored.
>
> The warning fixes hides the fact that sparc64 is not yet y2038 prepared,
> and it would be preferable if someone knowledgeable would fix this
> poperly.
The clone3 bug has been around for ages, it's probably not even that
hard to fix and just needs a little bit of testing.
If anyone wants to work on the time64 support for the vdso, I can
explain the details for how it's done.
Both of these are real bugs that should be addressed, unlike
the other warning fixes that are mostly cosmetic aside from
allowing the build with CONFIG_WERROR=y.
Arnd
next prev parent reply other threads:[~2024-03-30 10:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-30 9:57 Sam Ravnborg via B4 Relay
2024-03-30 9:57 ` [PATCH 01/10] sparc64: Fix prototype warning for init_vdso_image Sam Ravnborg via B4 Relay
2024-03-30 9:57 ` [PATCH 02/10] sparc64: Fix prototype warnings in traps_64.c Sam Ravnborg via B4 Relay
2024-03-30 9:57 ` [PATCH 03/10] sparc64: Fix prototype warning for vmemmap_free Sam Ravnborg via B4 Relay
2024-03-30 9:57 ` [PATCH 04/10] sparc64: Fix prototype warning for alloc_irqstack_bootmem Sam Ravnborg via B4 Relay
2024-03-30 9:57 ` [PATCH 05/10] sparc64: Fix prototype warning for uprobe_trap Sam Ravnborg via B4 Relay
2024-03-30 9:57 ` [PATCH 06/10] sparc64: Fix prototype warning for dma_4v_iotsb_bind Sam Ravnborg via B4 Relay
2024-03-30 9:57 ` [PATCH 07/10] sparc64: Fix prototype warnings in adi_64.c Sam Ravnborg via B4 Relay
2024-03-30 9:57 ` [PATCH 08/10] sparc64: Fix prototype warning for sched_clock Sam Ravnborg via B4 Relay
2024-03-30 9:57 ` [PATCH 09/10] sparc64: Fix number of online CPUs Sam Ravnborg via B4 Relay
2024-03-30 9:57 ` [PATCH 10/10] sparc64: Fix prototype warnings for vdso Sam Ravnborg via B4 Relay
2024-03-30 10:16 ` Arnd Bergmann
2024-03-30 10:19 ` Arnd Bergmann [this message]
2024-03-30 18:39 ` [PATCH 00/10] sparc64: Fix CPU online bug and warning fixes Sam Ravnborg
2024-04-22 13:11 ` Andreas Larsson
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=4e57929b-1539-4a25-ab05-a2a9e04ecc1d@app.fastmail.com \
--to=arnd@arndb.de \
--cc=andreas@gaisler.com \
--cc=atish.patra@oracle.com \
--cc=bob.picco@oracle.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nbowler@draconx.ca \
--cc=sam@ravnborg.org \
--cc=sparclinux@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=vijay.ac.kumar@oracle.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
all inboxes | Powered by JetHome®