From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Manikanta Maddireddy <mmaddireddy@nvidia.com>,
linux-tegra@vger.kernel.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pci: tegra: add MSI dependency
Date: Wed, 14 Mar 2018 10:51:07 +0000 [thread overview]
Message-ID: <20180314105107.GA27699@e107981-ln.cambridge.arm.com> (raw)
In-Reply-To: <20180313115218.2246372-1-arnd@arndb.de>
On Tue, Mar 13, 2018 at 12:52:05PM +0100, Arnd Bergmann wrote:
> Building the tegra PCIe host driver without MSI results in a link
> failure:
>
> drivers/pci/host/pci-tegra.o:(.data+0x70): undefined reference to `pci_msi_unmask_irq'
> drivers/pci/host/pci-tegra.o:(.data+0x74): undefined reference to `pci_msi_mask_irq'
>
> This adds the same dependency that everyone else uses.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
> drivers/pci/host/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
Applied to pci/host/misc for v4.17, thanks.
Lorenzo
> diff --git a/drivers/pci/host/Kconfig b/drivers/pci/host/Kconfig
> index 1fcdc890acc7..65b4afb8d11d 100644
> --- a/drivers/pci/host/Kconfig
> +++ b/drivers/pci/host/Kconfig
> @@ -38,6 +38,7 @@ config PCI_FTPCI100
> config PCI_TEGRA
> bool "NVIDIA Tegra PCIe controller"
> depends on ARCH_TEGRA && MMU
> + depends on PCI_MSI_IRQ_DOMAIN
> help
> Say Y here if you want support for the PCIe host controller found
> on NVIDIA Tegra SoCs.
> --
> 2.9.0
>
next prev parent reply other threads:[~2018-03-14 10:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-13 11:52 [PATCH] pci: tegra: add MSI dependency Arnd Bergmann
2018-03-14 10:51 ` Lorenzo Pieralisi [this message]
2018-03-14 11:45 ` Thierry Reding
2018-03-14 12:06 ` Arnd Bergmann
2018-03-14 12:13 ` Thierry Reding
2018-03-14 18:34 ` Lorenzo Pieralisi
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=20180314105107.GA27699@e107981-ln.cambridge.arm.com \
--to=lorenzo.pieralisi@arm.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mmaddireddy@nvidia.com \
/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).