From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com ([134.134.136.24]:34275 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751527AbbHLW7i (ORCPT ); Wed, 12 Aug 2015 18:59:38 -0400 Message-ID: <55CBCF96.7060102@intel.com> Date: Wed, 12 Aug 2015 15:58:30 -0700 From: Tadeusz Struk MIME-Version: 1.0 To: Stephen Rothwell , Randy Dunlap CC: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, linux-pci , Herbert Xu , Michal Marek Subject: Re: linux-next: Tree for Aug 12 (include/linux/pci.h) References: <20150812233914.451d1fcf@canb.auug.org.au> <55CB8AF0.4060905@infradead.org> <20150813075322.064035f8@canb.auug.org.au> In-Reply-To: <20150813075322.064035f8@canb.auug.org.au> Content-Type: text/plain; charset=utf-8 Sender: linux-pci-owner@vger.kernel.org List-ID: Hi, On 08/12/2015 02:53 PM, Stephen Rothwell wrote: > On Wed, 12 Aug 2015 11:05:36 -0700 Randy Dunlap 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?