From: Lu Baolu <baolu.lu@linux.intel.com>
To: Joerg Roedel <joro@8bytes.org>, iommu@lists.linux-foundation.org
Cc: David Woodhouse <dwmw2@infradead.org>,
Joerg Roedel <jroedel@suse.de>, CQ Tang <cq.tang@intel.com>,
Ashok Raj <ashok.raj@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iommu/vt-d: Fix compile warning from intel-svm.h
Date: Tue, 11 Feb 2020 08:24:24 +0800 [thread overview]
Message-ID: <723094c4-1c4c-7d52-d737-d0f201e634d6@linux.intel.com> (raw)
In-Reply-To: <20200210093656.8961-1-joro@8bytes.org>
Hi Joerg,
On 2020/2/10 17:36, Joerg Roedel wrote:
> From: Joerg Roedel <jroedel@suse.de>
>
> The intel_svm_is_pasid_valid() needs to be marked inline, otherwise it
> causes the compile warning below:
>
> CC [M] drivers/dma/idxd/cdev.o
> In file included from drivers/dma/idxd/cdev.c:9:0:
> ./include/linux/intel-svm.h:125:12: warning: ‘intel_svm_is_pasid_valid’ defined but not used [-Wunused-function]
> static int intel_svm_is_pasid_valid(struct device *dev, int pasid)
> ^~~~~~~~~~~~~~~~~~~~~~~~
>
> Reported-by: Borislav Petkov <bp@alien8.de>
> Fixes: 15060aba71711 ('iommu/vt-d: Helper function to query if a pasid has any active users')
> Signed-off-by: Joerg Roedel <jroedel@suse.de>
Acked-by: Lu Baolu <baolu.lu@linux.intel.com>
Best regards,
baolu
> ---
> include/linux/intel-svm.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/linux/intel-svm.h b/include/linux/intel-svm.h
> index 94f047a8a845..d7c403d0dd27 100644
> --- a/include/linux/intel-svm.h
> +++ b/include/linux/intel-svm.h
> @@ -122,7 +122,7 @@ static inline int intel_svm_unbind_mm(struct device *dev, int pasid)
> BUG();
> }
>
> -static int intel_svm_is_pasid_valid(struct device *dev, int pasid)
> +static inline int intel_svm_is_pasid_valid(struct device *dev, int pasid)
> {
> return -EINVAL;
> }
>
prev parent reply other threads:[~2020-02-11 0:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 9:36 Joerg Roedel
2020-02-11 0:24 ` Lu Baolu [this message]
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=723094c4-1c4c-7d52-d737-d0f201e634d6@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=ashok.raj@intel.com \
--cc=cq.tang@intel.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=jroedel@suse.de \
--cc=linux-kernel@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®