From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Andrew Morton <akpm@linux-foundation.org>,
Douglas Anderson <dianders@chromium.org>,
Petr Mladek <pmladek@suse.com>
Subject: Re: linux-next: Tree for Jun 28 (arch/powerpc/platforms/pseries/mobility.c)
Date: Wed, 28 Jun 2023 22:07:17 -0700 [thread overview]
Message-ID: <af19b76d-aa4b-6c88-9cac-eae4b2072497@infradead.org> (raw)
In-Reply-To: <20230628142751.0527c993@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1047 bytes --]
On 6/27/23 21:27, Stephen Rothwell wrote:
> Hi all,
>
> Please do *not* add any v5.6 related stuff to your linux-next included
> branches until after v5.5-rc1 has been released.
>
> Changes since 20230627:
>
on powerpc64, when
# CONFIG_HARDLOCKUP_DETECTOR is not set:
../arch/powerpc/platforms/pseries/mobility.c: In function 'pseries_migrate_partition':
../arch/powerpc/platforms/pseries/mobility.c:753:17: error: implicit declaration of function 'watchdog_hardlockup_set_timeout_pct'; did you mean 'watchdog_hardlockup_stop'? [-Werror=implicit-function-declaration]
753 | watchdog_hardlockup_set_timeout_pct(factor);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| watchdog_hardlockup_stop
cc1: all warnings being treated as errors
Full randconfig file is attached.
If I blatantly modify include/linux/nmi.h with these comments, it builds OK:
//#if defined(CONFIG_HARDLOCKUP_DETECTOR_ARCH) || defined(CONFIG_HARDLOCKUP_DETECTOR_SPARC64)
#include <asm/nmi.h>
//#endif
--
~Randy
[-- Attachment #2: config-r2079.gz --]
[-- Type: application/gzip, Size: 44570 bytes --]
next prev parent reply other threads:[~2023-06-29 5:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 4:27 linux-next: Tree for Jun 28 Stephen Rothwell
2023-06-29 5:07 ` Randy Dunlap [this message]
2023-06-29 8:40 ` linux-next: Tree for Jun 28 (arch/powerpc/platforms/pseries/mobility.c) Petr Mladek
2023-06-29 19:51 ` Doug Anderson
2023-06-30 14:33 ` Petr Mladek
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=af19b76d-aa4b-6c88-9cac-eae4b2072497@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=dianders@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mpe@ellerman.id.au \
--cc=pmladek@suse.com \
--cc=sfr@canb.auug.org.au \
/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