From: Randy Dunlap <rdunlap@infradead.org>
To: Tadeusz Struk <tadeusz.struk@intel.com>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pci <linux-pci@vger.kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
Michal Marek <mmarek@suse.cz>
Subject: Re: linux-next: Tree for Aug 12 (include/linux/pci.h)
Date: Wed, 12 Aug 2015 17:16:39 -0700 [thread overview]
Message-ID: <55CBE1E7.60904@infradead.org> (raw)
In-Reply-To: <55CBCF96.7060102@intel.com>
On 08/12/15 15:58, Tadeusz Struk wrote:
> Hi,
> On 08/12/2015 02:53 PM, Stephen Rothwell wrote:
>> On Wed, 12 Aug 2015 11:05:36 -0700 Randy Dunlap <rdunlap@infradead.org> wrote:
>>>>
>>>> on i386 or x86_64:
>>>>
>>>> Many (repeated) errors like this one:
>>>>
>>>> ../include/linux/pci.h:390:12: error: ‘struct pci_dev’ has no member named ‘physfn’
>>>>
>>>> when CONFIG_PCI_ATS is not enabled.
>> Maybe caused by commit
>>
>> dd0f368398ea ("crypto: qat - Add qat dh895xcc VF driver")
>>
>> from the crypto tree Which adds a
>>
>> select PCI_IOV
>>
>> to drivers/crypto/qat/Kconfig without the necessary
>>
>> select PCI
>>
>> but PCI_IOV selects PCI_ATS, so I am not sure what happened here. I am
>> assuming that your config has PCI_IOV enabled? What about PCI?
>
> There is a patch submitted, but not yet applied
> https://patchwork.kernel.org/patch/6994171/
> maybe it will help?
Yes, that works for me. Thanks.
--
~Randy
next prev parent reply other threads:[~2015-08-13 0:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150812233914.451d1fcf@canb.auug.org.au>
2015-08-12 18:05 ` linux-next: Tree for Aug 12 (include/linux/pci.h) Randy Dunlap
2015-08-12 21:53 ` Stephen Rothwell
2015-08-12 22:58 ` Tadeusz Struk
2015-08-13 0:16 ` Randy Dunlap [this message]
2015-08-13 0:49 ` Stephen Rothwell
2015-08-20 6:16 ` Bjorn Helgaas
2015-08-20 6:18 ` Stephen Rothwell
2015-08-12 23:22 ` Randy Dunlap
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=55CBE1E7.60904@infradead.org \
--to=rdunlap@infradead.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=sfr@canb.auug.org.au \
--cc=tadeusz.struk@intel.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).