From: Daniel Palmer <daniel@0x0f.com>
To: gerg@linux-m68k.org, geert@linux-m68k.org
Cc: linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] m68k: Use macro to generate 68000 interrupt entry sleds
Date: Sun, 7 Jan 2024 22:17:56 +0900 [thread overview]
Message-ID: <CAFr9PX=-eC-FZmmOKK_beFvs05_moe8u0jGPrSyW5Xr=AagmTA@mail.gmail.com> (raw)
In-Reply-To: <20240107014248.3651022-1-daniel@0x0f.com>
Hi me,
On Sun, 7 Jan 2024 at 10:42, Daniel Palmer <daniel@0x0f.com> wrote:
<snip>
>
> --- a/arch/m68k/68000/ints.c
> +++ b/arch/m68k/68000/ints.c
> +asmlinkage irqreturn_t inthandler65(void);
> +asmlinkage irqreturn_t inthandler66(void);
> +asmlinkage irqreturn_t inthandler67(void);
> +asmlinkage irqreturn_t inthandler68(void);
> +asmlinkage irqreturn_t inthandler69(void);
> +asmlinkage irqreturn_t inthandler70(void);
> +asmlinkage irqreturn_t inthandler71(void);
>
> /* The 68k family did not have a good way to determine the source
> * of interrupts until later in the family. The EC000 core does
> --
> 2.43.0
There is a missing part of this that updates the symbols used when
populating the vector table that I missed when splitting this patch
out.
This will currently cause a build break that I didn't notice because
the change is actually in my tree.
I'll send a v2 if the general idea is ok.
Cheers,
Daniel
prev parent reply other threads:[~2024-01-07 13:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-07 1:42 [PATCH] m68k: Use macro to generate 68000 interrupt entry sleds Daniel Palmer
2024-01-07 13:17 ` Daniel Palmer [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='CAFr9PX=-eC-FZmmOKK_beFvs05_moe8u0jGPrSyW5Xr=AagmTA@mail.gmail.com' \
--to=daniel@0x0f.com \
--cc=geert@linux-m68k.org \
--cc=gerg@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).