From: Lukas Wunner <lukas@wunner.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Simona Vetter" <simona.vetter@ffwll.ch>,
"Jeff Hugo" <jeff.hugo@oss.qualcomm.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Krzysztof Wilczy??ski" <kwilczynski@kernel.org>,
"Intel Graphics" <intel-gfx@lists.freedesktop.org>,
DRI <dri-devel@lists.freedesktop.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux Next Mailing List" <linux-next@vger.kernel.org>
Subject: Re: linux-next: semantic conflict between the drm-misc tree and Linus' tree
Date: Tue, 10 Jun 2025 05:46:27 +0200 [thread overview]
Message-ID: <aEeqkw670ZcuDdZO@wunner.de> (raw)
In-Reply-To: <20250610124809.1e1ff0cd@canb.auug.org.au>
On Tue, Jun 10, 2025 at 12:48:09PM +1000, Stephen Rothwell wrote:
> After merging the drm-misc tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/accel/qaic/qaic_ras.c: In function 'decode_ras_msg':
> drivers/accel/qaic/qaic_ras.c:325:17: error: implicit declaration of function 'pci_printk'; did you mean 'pci_intx'? [-Wimplicit-function-declaration]
> 325 | pci_printk(level, qdev->pdev, "RAS event.\nClass:%s\nDescription:%s %s %s\nError Threshold for this report %d\nSyndrome:\n 0x%llx\n 0x%llx\n 0x%llx\n 0x%llx\n 0x%llx\n 0x%llx\n 0x%llx\n 0x%llx\n",
> | ^~~~~~~~~~
> | pci_intx
>
> Caused by commit
>
> c11a50b170e7 ("accel/qaic: Add Reliability, Accessibility, Serviceability (RAS)")
>
> interacting with commit
>
> 1c8a0ed2043c ("PCI: Remove unused pci_printk()")
>
> from Linus' tree (in v6.16-rc1).
>
> As a fix up patch would be a bit of a mess, I have used the drm-misc
> tree from next-20250606 for today.
The simplest fix is to use dev_printk() and replace qdev->pdev with
&qdev->pdev->dev.
The PCI core already contains one occurrence of dev_printk() in
drivers/pci/tlp.c (introduced this cycle - 82013ff394ea).
Additionally drivers/pci/aer.c goes so far as to define a custom
aer_printk() for lack of a pci_printk().
drivers/pci/controller/dwc/pcie-tegra194.c contains further
occurrences of dev_printk() which could use pci_printk() instead.
Those occurrences suggest that the removal of pci_printk() was
perhaps uncalled for.
Thanks,
Lukas
next prev parent reply other threads:[~2025-06-10 3:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 2:48 linux-next: semantic conflict between the drm-misc tree and Linus' tree Stephen Rothwell
2025-06-10 3:46 ` Lukas Wunner [this message]
2025-06-10 15:22 ` Jeff Hugo
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=aEeqkw670ZcuDdZO@wunner.de \
--to=lukas@wunner.de \
--cc=bhelgaas@google.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jeff.hugo@oss.qualcomm.com \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=simona.vetter@ffwll.ch \
/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