From: Helge Deller <deller@gmx.de>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [linux-next:master 2035/3509] ERROR: modpost: "iosapic_serial_irq" [drivers/tty/serial/8250/8250_parisc.ko] undefined!
Date: Thu, 27 Oct 2022 09:19:20 +0200 [thread overview]
Message-ID: <6a1a6b3b-a3dd-ffcf-aa2e-e0722b389bd4@gmx.de> (raw)
In-Reply-To: <202210270740.vg9kIwKJ-lkp@intel.com>
On 10/27/22 02:04, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 60eac8672b5b6061ec07499c0f1b79f6d94311ce
> commit: 9e4e2ce1a78ed92ed91135e90c85f27d75388129 [2035/3509] parisc/serial: Rename 8250_gsc.c to 8250_parisc.c
> config: parisc-randconfig-s031-20221026
> compiler: hppa64-linux-gcc (GCC) 12.1.0
>
>>> ERROR: modpost: "iosapic_serial_irq" [drivers/tty/serial/8250/8250_parisc.ko] undefined!
Nice catch.
I fixed it with a commit to the parisc git tree, which exports that symbol.
So this error should disappear soon in for-next.
Thanks,
Helge
prev parent reply other threads:[~2022-10-27 7:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 0:04 [linux-next:master 2035/3509] ERROR: modpost: "iosapic_serial_irq" [drivers/tty/serial/8250/8250_parisc.ko] undefined! kernel test robot
2022-10-27 7:19 ` Helge Deller [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=6a1a6b3b-a3dd-ffcf-aa2e-e0722b389bd4@gmx.de \
--to=deller@gmx.de \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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 NNTP newsgroup(s).