mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Randy Dunlap <rdunlap@infradead.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Nipun Gupta <nipun.gupta@amd.com>,
	Nikhil Agarwal <nikhil.agarwal@amd.com>
Subject: Re: linux-next: Tree for Jul 15 (drivers/cdx/cdx.o)
Date: Wed, 16 Jul 2025 08:19:50 +0200	[thread overview]
Message-ID: <5a000710-516d-462f-8c0d-9e58e4abf4c3@linaro.org> (raw)
In-Reply-To: <b2c54a12-480c-448a-8b90-333cb03d9c14@infradead.org>

On 16/07/2025 03:32, Randy Dunlap wrote:
> 
> 
> On 7/15/25 3:45 AM, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20250714:
>>
> 
> on x86_64, when
> CONFIG_COMPILE_TEST=y
> # CONFIG_PCI_MSI is not set
> CONFIG_CDX_BUS=y
> # CONFIG_CDX_CONTROLLER is not set
> # CONFIG_GENERIC_MSI_IRQ is not set
> 
> ld: drivers/cdx/cdx.o: in function `cdx_probe':
> /home/rdunlap/lnx/next/linux-next-20250715/X64/../drivers/cdx/cdx.c:314:(.text+0xc8b): undefined reference to `msi_setup_device_data'

Thanks, I can reproduce it.

The driver was never selecting CONFIG_GENERIC_MSI_IRQ and that part was
missing. I wonder why arm64 compile testing without GIC, SMMU and other
drivers, which select it, never reported it.

I'll send a fix.


Best regards,
Krzysztof

  reply	other threads:[~2025-07-16  6:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-15 10:45 linux-next: Tree for Jul 15 Stephen Rothwell
2025-07-16  1:32 ` linux-next: Tree for Jul 15 (drivers/cdx/cdx.o) Randy Dunlap
2025-07-16  6:19   ` Krzysztof Kozlowski [this message]
2025-07-16  1:42 ` linux-next: Tree for Jul 15 (drivers/tty/serial/8250/8250_ce4100.c) Randy Dunlap
2025-07-16  9:33   ` Andy Shevchenko

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=5a000710-516d-462f-8c0d-9e58e4abf4c3@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=nikhil.agarwal@amd.com \
    --cc=nipun.gupta@amd.com \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    /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®