linux-kernel - RE: linux-next: build failure after merge of the pci tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <TYBPR01MB5341114CB14098217765790BD8D8A@TYBPR01MB5341.jpnprd01.prod.outlook.com>
Date:   Mon, 23 Oct 2023 07:30:08 +0000
From:   Yoshihiro Shimoda <yoshihiro.shimoda.uh@...esas.com>
To:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Bjorn Helgaas <bhelgaas@...gle.com>,
        Lorenzo Pieralisi <lpieralisi@...nel.org>,
        Krzysztof Wilczyński <kw@...ux.com>
CC:     Krzysztof Wilczyński <kwilczynski@...nel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: RE: linux-next: build failure after merge of the pci tree

Hi Stephen,

> From: Stephen Rothwell, Sent: Monday, October 23, 2023 9:06 AM
> 
> Hi all,
> 
> After merging the pci tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
> 
> ERROR: modpost: "dw_pcie_write_dbi2" [drivers/pci/controller/dwc/pcie-rcar-gen4.ko] undefined!
> 
> Caused by commit
> 
>   8227bf7a81e6 ("PCI: rcar-gen4: Add R-Car Gen4 PCIe controller support for host mode")
> 
> or
> 
>   d3c54d8ba855 ("PCI: rcar-gen4: Add endpoint mode support")
> 
> I have used the pci tree from next-20231020 for today.

Thank you for the report!

Bjorn, Krzysztof, I should have added the following patch on patch-set v25.
However, I completely forgot it...
https://lore.kernel.org/linux-pci/20230926122431.3974714-8-yoshihiro.shimoda.uh@renesas.com/

I confirmed that the patch above can be applied on the latest pci.git / next branch.
However, should I resend whole patches with the patch above as v26?

Best regards,
Yoshihiro Shimoda

> --
> Cheers,
> Stephen Rothwell