[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250221165035.GA3992086@rocinante>
Date: Sat, 22 Feb 2025 01:50:35 +0900
From: Krzysztof WilczyĆski <kw@...ux.com>
To: Stanimir Varbanov <svarbanov@...e.de>
Cc: Jim Quinlan <jim2101024@...il.com>, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-rpi-kernel@...ts.infradead.org, linux-pci@...r.kernel.org,
Broadcom internal kernel review list <bcm-kernel-feedback-list@...adcom.com>,
Thomas Gleixner <tglx@...utronix.de>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
Florian Fainelli <florian.fainelli@...adcom.com>,
Nicolas Saenz Julienne <nsaenz@...nel.org>,
Bjorn Helgaas <bhelgaas@...gle.com>,
Lorenzo Pieralisi <lpieralisi@...nel.org>,
Philipp Zabel <p.zabel@...gutronix.de>,
Andrea della Porta <andrea.porta@...e.com>,
Phil Elwell <phil@...pberrypi.com>,
Jonathan Bell <jonathan@...pberrypi.com>,
Dave Stevenson <dave.stevenson@...pberrypi.com>
Subject: Re: [PATCH v5 -next 04/11] PCI: brcmstb: Reuse config structure
Hello,
> > Sorry for the late notice but I get a compilation error on this commit:
> >
> > drivers/pci/controller/pcie-brcmstb.c: In function 'brcm_pcie_turn_off':
> > drivers/pci/controller/pcie-brcmstb.c:1492:14: error: 'struct
> > brcm_pcie' has no member named 'bridge_sw_init_set'; did you mean
> > 'bridge_reset'?
> > ret = pcie->bridge_sw_init_set(pcie, 1);
> > ^~~~~~~~~~~~~~~~~~
> > bridge_reset
> > make[5]: *** [scripts/Makefile.build:194:
> > drivers/pci/controller/pcie-brcmstb.o] Error 1
> >
> > It appears to be fixed with the subsequent commit "PCI: brcmstb: Add
> > bcm2712 support".
> >
> > Can you please look into this and see if you get the same results?
>
> Ah, it is my fault. Thanks for spotting this. This must have happened
> when moving this patch earlier in the series.
No worries. Things happen. We can fix everything. :)
> Krzystof,
>
> I could send a new version of the series or the other option could be to
> rework those two patches in controller/brcmstb?
Happy to modify things on the branch directly. But if it's easier to send
a new version, then feel free. Either approach would work. :)
> I will post later the fixes here if you choose the second option.
Thank you, sir, for a prompt reply! Appreciated.
Krzysztof
Powered by blists - more mailing lists