From: "Arnd Bergmann" <arnd@arndb.de>
To: "Randy Dunlap" <rdunlap@infradead.org>,
"kernel test robot" <lkp@intel.com>,
"Masahiro Yamada" <masahiroy@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
"Nicolas Schier" <nicolas@fjasle.eu>,
"Jiaxun Yang" <jiaxun.yang@flygoat.com>,
linux-mips@vger.kernel.org
Subject: Re: pm.c:undefined reference to `i8042_command'
Date: Wed, 06 Dec 2023 07:52:58 +0100 [thread overview]
Message-ID: <f712a65b-4984-46e8-bd43-1309b5cd41f0@app.fastmail.com> (raw)
In-Reply-To: <5f1caaf8-1edf-444a-b017-c4d08e52213b@infradead.org>
On Wed, Dec 6, 2023, at 06:24, Randy Dunlap wrote:
>> All errors (new ones prefixed by >>):
>>
>> mips64el-linux-ld: arch/mips/loongson2ef/lemote-2f/pm.o: in function `setup_wakeup_events':
>>>> pm.c:(.text+0x118): undefined reference to `i8042_command'
>>>> mips64el-linux-ld: pm.c:(.text+0x154): undefined reference to `i8042_command'
>
>
> How do we feel about this?
> I suppose that an ARCH or mach or board should know what it requires.
>
>
> ---
> arch/mips/loongson2ef/Kconfig | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff -- a/arch/mips/loongson2ef/Kconfig b/arch/mips/loongson2ef/Kconfig
> --- a/arch/mips/loongson2ef/Kconfig
> +++ b/arch/mips/loongson2ef/Kconfig
> @@ -40,6 +40,9 @@ config LEMOTE_MACH2F
> select ARCH_HAS_PHYS_TO_DMA
> select ARCH_MIGHT_HAVE_PC_PARPORT
> select ARCH_MIGHT_HAVE_PC_SERIO
> + select INPUT
> + select SERIO
> + select SERIO_I8042
> select BOARD_SCACHE
> select BOOT_ELF32
I think it's bad style to force-select an optional subsystem.
How about making the entire file optional? It seems that there
are already __weak functions in its place.
--- a/arch/mips/loongson2ef/lemote-2f/Makefile
+++ b/arch/mips/loongson2ef/lemote-2f/Makefile
@@ -8,5 +8,6 @@ obj-y += clock.o machtype.o irq.o reset.o dma.o ec_kb3310b.o
#
# Suspend Support
#
-
+ifdef CONFIG_SERIO_I8042
obj-$(CONFIG_SUSPEND) += pm.o
+endif
Arnd
next prev parent reply other threads:[~2023-12-06 6:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 12:02 kernel test robot
2023-12-06 5:24 ` Randy Dunlap
2023-12-06 6:52 ` Arnd Bergmann [this message]
2023-12-06 17:26 ` Randy Dunlap
2023-12-07 1:21 ` Jiaxun Yang
2023-12-14 19:54 ` Arnd Bergmann
2023-12-14 23:57 ` Randy Dunlap
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=f712a65b-4984-46e8-bd43-1309b5cd41f0@app.fastmail.com \
--to=arnd@arndb.de \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=lkp@intel.com \
--cc=masahiroy@kernel.org \
--cc=nicolas@fjasle.eu \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rdunlap@infradead.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
all inboxes | Powered by JetHome®