From: Ulrich Hecht <uli@fpond.eu>
To: cip-dev@lists.cip-project.org,
Michael Schmitz <schmitzmic@gmail.com>,
linux-m68k@vger.kernel.org
Cc: Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [cip-dev] [PATCH] m68k: include module.h to make use of exception handling in traps.c
Date: Fri, 2 Feb 2024 04:54:14 +0100 (CET) [thread overview]
Message-ID: <1550495460.64761.1706846054273@webmail.strato.com> (raw)
In-Reply-To: <20240201204329.24202-1-schmitzmic@gmail.com>
> On 02/01/2024 9:43 PM CET Michael Schmitz <schmitzmic@gmail.com> wrote:
>
>
> Backporting commit 513138a14063760e (m68k: Only force 030
> bus error if PC not in exception table) to v4.4 by the CIP
> project revealed a build error due to extable.h not yet
> available.
>
> extable.h was split off module.h in v4.8 (commit
> 0ef7653797addea8) so amend 513138a14063760e accordingly.
>
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202401302324.d3o6tgup-lkp@intel.com/
> Cc: <cip-dev@lists.cip-project.org> # 4.4
> Cc: Ulrich Hecht <uli@fpond.eu>
> Cc: Geert Uytterhoeven <geert@linux-m68k.org>
> Signed-off-by: Michael Schmitz <schmitzmic@gmail.com>
> ---
> arch/m68k/kernel/traps.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/m68k/kernel/traps.c b/arch/m68k/kernel/traps.c
> index c547140b8325..2209214cf91c 100644
> --- a/arch/m68k/kernel/traps.c
> +++ b/arch/m68k/kernel/traps.c
> @@ -29,7 +29,7 @@
> #include <linux/init.h>
> #include <linux/ptrace.h>
> #include <linux/kallsyms.h>
> -#include <linux/extable.h>
> +#include <linux/module.h>
>
> #include <asm/setup.h>
> #include <asm/fpu.h>
> --
> 2.17.1
Applied, thank you.
CU
Uli
prev parent reply other threads:[~2024-02-02 3:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 20:43 [PATCH] m68k: include module.h to make use of exception handling in traps.c Michael Schmitz
2024-02-02 3:54 ` Ulrich Hecht [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=1550495460.64761.1706846054273@webmail.strato.com \
--to=uli@fpond.eu \
--cc=cip-dev@lists.cip-project.org \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
--cc=schmitzmic@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).