From: Siddharth Vadapalli <s-vadapalli@ti.com>
To: kernel test robot <lkp@intel.com>
Cc: <lpieralisi@kernel.org>, <kwilczynski@kernel.org>,
<mani@kernel.org>, <robh@kernel.org>, <bhelgaas@google.com>,
<jingoohan1@gmail.com>, <quic_wenbyao@quicinc.com>,
<inochiama@gmail.com>, <mayank.rana@oss.qualcomm.com>,
<thippeswamy.havalige@amd.com>, <shradha.t@samsung.com>,
<cassel@kernel.org>, <kishon@kernel.org>,
<sergio.paracuellos@gmail.com>, <18255117159@163.com>,
<rongqianfeng@vivo.com>, <jirislaby@kernel.org>,
<oe-kbuild-all@lists.linux.dev>, <linux-pci@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <srk@ti.com>,
<s-vadapalli@ti.com>
Subject: Re: [PATCH v4 4/4] PCI: keystone: Add support to build as a loadable module
Date: Tue, 28 Oct 2025 10:24:51 +0530 [thread overview]
Message-ID: <44b90ca1a10fe737cb20b76327846c5cda420924.camel@ti.com> (raw)
In-Reply-To: <202510281008.jw19XuyP-lkp@intel.com>
On Tue, 2025-10-28 at 11:06 +0800, kernel test robot wrote:
> Hi Siddharth,
>
> kernel test robot noticed the following build errors:
>
> [auto build test ERROR on pci/next]
> [also build test ERROR on pci/for-linus linus/master v6.18-rc3 next-20251027]
> [If your patch is applied to the wrong git tree, kindly drop us a note.
> And when submitting patch, we suggest to use '--base' as documented in
> https://git-scm.com/docs/git-format-patch#_base_tree_information]
>
> url: https://github.com/intel-lab-lkp/linux/commits/Siddharth-Vadapalli/PCI-Export-pci_get_host_bridge_device-for-use-by-pci-keystone/20251022-180213
> base: https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git next
> patch link: https://lore.kernel.org/r/20251022095724.997218-5-s-vadapalli%40ti.com
> patch subject: [PATCH v4 4/4] PCI: keystone: Add support to build as a loadable module
> config: arm-allmodconfig (https://download.01.org/0day-ci/archive/20251028/202510281008.jw19XuyP-lkp@intel.com/config)
> compiler: arm-linux-gnueabi-gcc (GCC) 15.1.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251028/202510281008.jw19XuyP-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> > Reported-by: kernel test robot <lkp@intel.com>
> > Closes: https://lore.kernel.org/oe-kbuild-all/202510281008.jw19XuyP-lkp@intel.com/
>
> All errors (new ones prefixed by >>, old ones prefixed by <<):
>
> WARNING: modpost: missing MODULE_DESCRIPTION() in arch/arm/probes/kprobes/test-kprobes.o
> > > ERROR: modpost: "hook_fault_code" [drivers/pci/controller/dwc/pci-keystone.ko] undefined!
> ERROR: modpost: "__ffsdi2" [drivers/spi/spi-amlogic-spifc-a4.ko] undefined!
I had built the driver for ARM64 platforms but missed building it for ARM32
platforms. I will fix the build error for ARM32 platforms and will post the
v5 series.
Regards,
Siddharth.
next prev parent reply other threads:[~2025-10-28 4:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 9:57 [PATCH v4 0/4] PCI: Keystone: Enable loadable module support Siddharth Vadapalli
2025-10-22 9:57 ` [PATCH v4 1/4] PCI: Export pci_get_host_bridge_device() for use by pci-keystone Siddharth Vadapalli
2025-10-22 9:57 ` [PATCH v4 2/4] PCI: dwc: Export dw_pcie_allocate_domains() and dw_pcie_ep_raise_msix_irq() Siddharth Vadapalli
2025-10-22 9:57 ` [PATCH v4 3/4] PCI: keystone: Exit ks_pcie_probe() for invalid mode Siddharth Vadapalli
2025-10-22 9:57 ` [PATCH v4 4/4] PCI: keystone: Add support to build as a loadable module Siddharth Vadapalli
2025-10-28 3:06 ` kernel test robot
2025-10-28 4:54 ` Siddharth Vadapalli [this message]
2025-10-29 8:36 ` Siddharth Vadapalli
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=44b90ca1a10fe737cb20b76327846c5cda420924.camel@ti.com \
--to=s-vadapalli@ti.com \
--cc=18255117159@163.com \
--cc=bhelgaas@google.com \
--cc=cassel@kernel.org \
--cc=inochiama@gmail.com \
--cc=jingoohan1@gmail.com \
--cc=jirislaby@kernel.org \
--cc=kishon@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=mayank.rana@oss.qualcomm.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=quic_wenbyao@quicinc.com \
--cc=robh@kernel.org \
--cc=rongqianfeng@vivo.com \
--cc=sergio.paracuellos@gmail.com \
--cc=shradha.t@samsung.com \
--cc=srk@ti.com \
--cc=thippeswamy.havalige@amd.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
all inboxes | Powered by JetHome®