From: Randy Dunlap <rdunlap@infradead.org>
To: "Michael S. Tsirkin" <mst@redhat.com>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the vhost tree
Date: Wed, 9 Jul 2025 13:51:53 -0700 [thread overview]
Message-ID: <fdfc2aa4-09d6-4e5c-ae24-8d99b8bbe207@infradead.org> (raw)
In-Reply-To: <20250709155616-mutt-send-email-mst@kernel.org>
On 7/9/25 1:00 PM, Michael S. Tsirkin wrote:
> On Wed, Jul 09, 2025 at 10:19:05PM +1000, Stephen Rothwell wrote:
>> Hi all,
>>
>> After merging the vhost tree, today's linux-next build (x86_64
>> allnoconfig) failed like this:
>>
>> In file included from /home/sfr/next/next/arch/x86/events/amd/ibs.c:12:
>> /home/sfr/next/next/include/linux/pci.h: In function 'pci_set_disconnect_work':
>> /home/sfr/next/next/include/linux/pci.h:2738:14: error: implicit declaration of function 'pci_device_is_present'; did you mean 'pci_dev_present'? [-Wimplicit-function-declaration]
>> 2738 | if (!pci_device_is_present(pdev))
>> | ^~~~~~~~~~~~~~~~~~~~~
>> | pci_dev_present
>>
>> Caused by commit
>>
>> b7468115b604 ("pci: report surprise removal event")
>>
>> I have reverted that commit and the 4 following ones (just in case).
>>
>> --
>> Cheers,
>> Stephen Rothwell
>
>
>
> Weird:
> $ git grep pci_device_is_present include/linux/pci.h
> include/linux/pci.h:bool pci_device_is_present(struct pci_dev *pdev);
> include/linux/pci.h: if (!pci_device_is_present(pdev))
>
in x86_64 allnoconfig, CONFIG_PCI is not enabled.
The function is only defined when CONFIG_PCI is enabled.
> and of course I did build it ... which commit should I test?
>
The one that Stephen listed above?
--
~Randy
next prev parent reply other threads:[~2025-07-09 20:52 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-09 12:19 linux-next: build failure after merge of the vhost tree Stephen Rothwell
2025-07-09 20:00 ` Michael S. Tsirkin
2025-07-09 20:51 ` Randy Dunlap [this message]
2025-07-09 20:55 ` Michael S. Tsirkin
2025-07-09 20:50 ` Michael S. Tsirkin
-- strict thread matches above, loose matches on Subject: below --
2025-07-18 8:43 Stephen Rothwell
2024-02-29 3:55 Stephen Rothwell
2024-02-29 4:01 ` Xuan Zhuo
2024-02-29 7:21 ` Xuan Zhuo
2022-08-16 1:13 Stephen Rothwell
2022-06-01 1:42 Stephen Rothwell
2022-06-01 21:57 ` Michael S. Tsirkin
2022-06-02 3:19 ` Stephen Rothwell
2021-11-25 1:23 Stephen Rothwell
2021-09-06 2:49 Stephen Rothwell
2021-09-06 2:57 ` Yongji Xie
2021-07-08 1:08 Stephen Rothwell
2021-07-08 5:37 ` Michael S. Tsirkin
2020-08-04 5:11 Stephen Rothwell
2020-08-04 5:47 ` Guennadi Liakhovetski
2020-08-04 7:04 ` Guennadi Liakhovetski
2020-08-04 9:15 ` Michael S. Tsirkin
2020-07-30 7:52 Stephen Rothwell
2020-07-28 8:11 Stephen Rothwell
2020-07-29 14:08 ` Michael S. Tsirkin
2020-05-07 5:36 Stephen Rothwell
2020-04-07 3:05 Stephen Rothwell
2020-04-07 10:01 ` Michael S. Tsirkin
2020-04-07 18:58 ` Nathan Chancellor
2020-04-09 21:15 ` Michael S. Tsirkin
2019-12-04 3:24 Stephen Rothwell
2019-12-07 23:45 ` Stephen Rothwell
2019-12-09 15:24 ` Michael S. Tsirkin
2018-02-07 2:04 Stephen Rothwell
2018-02-07 2:52 ` Michael S. Tsirkin
2018-02-07 2:54 ` Stephen Rothwell
2018-02-07 2:57 ` Michael S. Tsirkin
2018-02-07 4:30 ` Stephen Rothwell
2017-03-30 4:25 Stephen Rothwell
2017-04-03 6:21 ` Stephen Rothwell
2014-06-10 4:12 Stephen Rothwell
2014-06-10 9:38 ` Michael S. Tsirkin
2014-06-03 8:38 Stephen Rothwell
2014-06-09 13:19 ` Michael S. Tsirkin
2013-05-22 4:37 Stephen Rothwell
2013-05-22 5:07 ` Michael S. Tsirkin
2013-05-22 9:03 ` Michael S. Tsirkin
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=fdfc2aa4-09d6-4e5c-ae24-8d99b8bbe207@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mst@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).