From: sathyanarayanan kuppuswamy <sathyanarayanan.kuppuswamy@linux.intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Joerg Roedel <joro@8bytes.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the iommu tree
Date: Wed, 27 Feb 2019 10:48:53 -0800 [thread overview]
Message-ID: <e4db08ff-256d-5273-f02e-f8d0533efe04@linux.intel.com> (raw)
In-Reply-To: <20190227132004.4d3a3da4@canb.auug.org.au>
Hi,
On 2/26/19 6:20 PM, Stephen Rothwell wrote:
> Hi Joerg,
>
> After merging the iommu tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
>
> In file included from drivers/pci/pci.c:32:
> include/linux/pci-ats.h:70:12: warning: 'pci_prg_resp_pasid_required' defined but not used [-Wunused-function]
> static int pci_prg_resp_pasid_required(struct pci_dev *pdev)
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> Introduced by commit
>
> e5567f5f6762 ("PCI/ATS: Add pci_prg_resp_pasid_required() interface.")
>
> The non CONFIG_PCI_PASID version needs an "inline".
I can submit the fix, but do we need a new patch to fix it or the
original patch can be updated ?
>
--
Sathyanarayanan Kuppuswamy
Linux kernel developer
next prev parent reply other threads:[~2019-02-27 18:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-27 2:20 linux-next: build warning after merge of the iommu tree Stephen Rothwell
2019-02-27 18:48 ` sathyanarayanan kuppuswamy [this message]
2019-02-27 19:26 ` [PATCH v1 1/1] PCI/ATS: Add inline to pci_prg_resp_pasid_required() Kuppuswamy Sathyanarayanan
-- strict thread matches above, loose matches on Subject: below --
2025-07-16 10:42 linux-next: build warning after merge of the iommu tree Stephen Rothwell
2025-07-17 10:04 ` Will Deacon
2024-07-09 9:06 Stephen Rothwell
2024-07-09 10:08 ` Will Deacon
2021-06-08 3:56 Stephen Rothwell
2018-11-08 1:39 Stephen Rothwell
2018-11-08 9:30 ` Joerg Roedel
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=e4db08ff-256d-5273-f02e-f8d0533efe04@linux.intel.com \
--to=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).