From: Thorsten Blum <thorsten.blum@linux.dev>
To: Daniel Palmer <daniel@0x0f.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] m68k: amiga: Mark amiga_reset() as __noreturn
Date: Fri, 26 Jun 2026 15:57:34 +0200 [thread overview]
Message-ID: <aj6FTgJ6mL36WrKV@linux.dev> (raw)
In-Reply-To: <CAFr9PX=gTnsBi4X+cFzMM3vfWE2mXO2ARPOEYe+ZWVJ4JWzPvg@mail.gmail.com>
Hi Daniel,
On Fri, Jun 26, 2026 at 10:49:59PM +0900, Daniel Palmer wrote:
> Hi Thorsten,
>
> On Fri, 26 Jun 2026 at 19:43, Thorsten Blum <thorsten.blum@linux.dev> wrote:
> >
> > Mark both the forward declaration and the function definition as
> > __noreturn, and remove the redundant redeclaration.
> >
> <snip>
>
> I tried to build and boot test this on my Amiga 4000 but the build is borken:
>
> UPD include/config/kernel.release
> UPD include/generated/utsrelease.h
> CC init/version.o
> AR init/built-in.a
> CC arch/m68k/amiga/config.o
> arch/m68k/amiga/config.c:546:1: error: attributes should be specified
> before the declarator in a function definition
> 546 | static void amiga_reset(void) __noreturn
> | ^~~~~~
> arch/m68k/amiga/config.c:99:13: warning: ‘amiga_reset’ used but never defined
> 99 | static void amiga_reset(void) __noreturn;
> | ^~~~~~~~~~~
>
> GCC version is: m68k-linux-gnu-gcc (Debian 15.2.0-17) 15.2.0
I also compiled it, but then moved the __noreturn to the end which is
apparently not allowed. Feel free to try:
static void __noreturn amiga_reset(void);
That should work. I'll send a v2 later.
Thanks,
Thorsten
prev parent reply other threads:[~2026-06-26 13:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-26 10:41 [PATCH] m68k: amiga: Mark amiga_reset() as __noreturn Thorsten Blum
2026-06-26 13:49 ` Daniel Palmer
2026-06-26 13:57 ` Thorsten Blum [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=aj6FTgJ6mL36WrKV@linux.dev \
--to=thorsten.blum@linux.dev \
--cc=daniel@0x0f.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox