From: Yanteng Si <siyanteng01@gmail.com>
To: sergio.paracuellos@gmail.com
Cc: Yanteng Si <siyanteng@loongson.cn>,
lorenzo.pieralisi@arm.com, robh@kernel.org, kw@linux.com,
bhelgaas@google.com, matthias.bgg@gmail.com,
p.zabel@pengutronix.de, linux-pci@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, tsbogend@alpha.franken.de,
linux-mips@vger.kernel.org, chenhuacai@kernel.org,
sterlingteng@gmail.com
Subject: [PATCH 0/2] drivers/mt7621: Fix build error ERROR: modpost:
Date: Wed, 27 Oct 2021 19:31:38 +0800 [thread overview]
Message-ID: <cover.1635333327.git.siyanteng@loongson.cn> (raw)
Since commit 2bdd5238e756 ("PCI: mt7621: Add MediaTek MT7621 PCIe host controller driver")
the MT7621 PCIe host controller driver is built as a module but no MODULE_*() attributes
were specified, causing a build error due to missing license information. At the same time,
modpost complains once these drivers become modules.
ERROR: modpost: missing MODULE_LICENSE() in drivers/pci/controller/pcie-mt7621.o
ERROR: modpost: "mips_cm_unlock_other" [drivers/pci/controller/pcie-mt7621.ko] undefined!
ERROR: modpost: "mips_cpc_base" [drivers/pci/controller/pcie-mt7621.ko] undefined!
ERROR: modpost: "mips_cm_lock_other" [drivers/pci/controller/pcie-mt7621.ko] undefined!
ERROR: modpost: "mips_cm_is64" [drivers/pci/controller/pcie-mt7621.ko] undefined!
ERROR: modpost: "mips_gcr_base" [drivers/pci/controller/pcie-mt7621.ko] undefined!
Let's just fix them.
Yanteng Si (2):
PCI: mt7621: Add MODULE_* macros to MT7621 PCIe host controller driver
PCI: mt7621: Export mips_cm/cpc/gcr_* to modules
arch/mips/kernel/mips-cm.c | 5 +++++
arch/mips/kernel/mips-cpc.c | 1 +
drivers/pci/controller/pcie-mt7621.c | 2 ++
3 files changed, 8 insertions(+)
--
2.27.0
next reply other threads:[~2021-10-27 11:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 11:31 Yanteng Si [this message]
2021-10-27 11:31 ` [PATCH 1/2] PCI: mt7621: Add MODULE_* macros to MT7621 PCIe host controller driver Yanteng Si
2021-10-27 11:59 ` Sergio Paracuellos
2021-10-28 1:45 ` yanteng si
2021-10-27 11:31 ` [PATCH 2/2] PCI: mt7621: Export mips_cm/cpc/gcr_* to modules Yanteng Si
2021-10-27 11:45 ` Sergio Paracuellos
2021-10-28 1:58 ` yanteng si
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=cover.1635333327.git.siyanteng@loongson.cn \
--to=siyanteng01@gmail.com \
--cc=bhelgaas@google.com \
--cc=chenhuacai@kernel.org \
--cc=kw@linux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=sergio.paracuellos@gmail.com \
--cc=siyanteng@loongson.cn \
--cc=sterlingteng@gmail.com \
--cc=tsbogend@alpha.franken.de \
/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).