[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <176604462693.840440.17361297043510952220.b4-ty@kernel.org>
Date: Thu, 18 Dec 2025 13:27:06 +0530
From: Manivannan Sadhasivam <manivannan.sadhasivam@....qualcomm.com>
To: vigneshr@...com, lpieralisi@...nel.org, kwilczynski@...nel.org,
robh@...nel.org, bhelgaas@...gle.com,
Siddharth Vadapalli <s-vadapalli@...com>
Cc: arnd@...db.de, kishon@...nel.org, stable@...r.kernel.org,
linux-omap@...r.kernel.org, linux-pci@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
srk@...com
Subject: Re: [PATCH] PCI: j721e: Add config guards for Cadence Host and
Endpoint library APIs
On Mon, 17 Nov 2025 17:02:06 +0530, Siddharth Vadapalli wrote:
> Commit under Fixes enabled loadable module support for the driver under
> the assumption that it shall be the sole user of the Cadence Host and
> Endpoint library APIs. This assumption guarantees that we won't end up
> in a case where the driver is built-in and the library support is built
> as a loadable module.
>
> With the introduction of [1], this assumption is no longer valid. The
> SG2042 driver could be built as a loadable module, implying that the
> Cadence Host library is also selected as a loadable module. However, the
> pci-j721e.c driver could be built-in as indicated by CONFIG_PCI_J721E=y
> due to which the Cadence Endpoint library is built-in. Despite the
> library drivers being built as specified by their respective consumers,
> since the 'pci-j721e.c' driver has references to the Cadence Host
> library APIs as well, we run into a build error as reported at [0].
>
> [...]
Applied, thanks!
[1/1] PCI: j721e: Add config guards for Cadence Host and Endpoint library APIs
commit: 4b361b1e92be255ff923453fe8db74086cc7cf66
Best regards,
--
Manivannan Sadhasivam <mani@...nel.org>
Powered by blists - more mailing lists