From: Kishon Vijay Abraham I <kishon@ti.com>
To: Bjorn Helgaas <helgaas@kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>, <linux-pci@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] PCI: endpoint: PCI_ENDPOINT should depend on HAS_DMA
Date: Tue, 23 May 2017 12:13:22 +0530 [thread overview]
Message-ID: <c54dfb8a-68ac-dc7b-f9d6-43e1ba391275@ti.com> (raw)
In-Reply-To: <20170522212640.GD19733@bhelgaas-glaptop.roam.corp.google.com>
Hi Bjorn,
On Tuesday 23 May 2017 02:56 AM, Bjorn Helgaas wrote:
> On Tue, May 16, 2017 at 07:21:08PM +0200, Geert Uytterhoeven wrote:
>> If NO_DMA=y:
>>
>> drivers/built-in.o: In function `__pci_epc_create':
>> (.text+0xef4e): undefined reference to `bad_dma_ops'
>> drivers/built-in.o: In function `pci_epc_add_epf':
>> (.text+0xf676): undefined reference to `bad_dma_ops'
>> drivers/built-in.o: In function `pci_epf_alloc_space':
>> (.text+0xfa32): undefined reference to `bad_dma_ops'
>> drivers/built-in.o: In function `pci_epf_free_space':
>> (.text+0xfac4): undefined reference to `bad_dma_ops'
>>
>> Add a dependency on HAS_DMA to fix this.
>>
>> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
>
> Applied to for-linus for v4.12, thanks!
>
>> ---
>> Should PCI_ENDPOINT depend on CONFIG_PCI instead?
>
> I *think* we want HAS_DMA, not CONFIG_PCI, because CONFIG_PCI means we
> want the infrastructure for PCI host bridges, enumerating children of
> the bridges, etc. I think we want to allow PCI_ENDPOINT without all
> that.
>
> Kishon?
right. CONFIG_PCI is for enabling the host infrastructure and PCI_ENDPOINT and
CONFIG_PCI should be completely independent of each other.
Thanks
Kishon
next prev parent reply other threads:[~2017-05-23 6:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 17:21 Geert Uytterhoeven
2017-05-22 21:26 ` Bjorn Helgaas
2017-05-23 6:43 ` Kishon Vijay Abraham I [this message]
2017-05-23 7:12 ` Geert Uytterhoeven
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=c54dfb8a-68ac-dc7b-f9d6-43e1ba391275@ti.com \
--to=kishon@ti.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=geert@linux-m68k.org \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
/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
all inboxes | Powered by JetHome®