From: Samuel Zou <zou_wei@huawei.com>
To: Santosh Sivaraj <santosh@fossix.org>, <dan.j.williams@intel.com>,
<vishal.l.verma@intel.com>, <dave.jiang@intel.com>,
<ira.weiny@intel.com>
Cc: <linux-nvdimm@lists.01.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next] tools/testing/nvdimm: Make symbol '__nfit_test_ioremap' static
Date: Tue, 20 Apr 2021 15:19:15 +0800 [thread overview]
Message-ID: <066633f6-e624-54ef-0de0-5589305fdbe3@huawei.com> (raw)
In-Reply-To: <87h7k1zco0.fsf@fossix.org>
Hi Santosh,
Thanks for your review, and sorry for my mistake. I will send the v2 soon.
On 2021/4/20 14:35, Santosh Sivaraj wrote:
>
> Hi Zou,
>
> Zou Wei <zou_wei@huawei.com> writes:
>
>> The sparse tool complains as follows:
>>
>> tools/testing/nvdimm/test/iomap.c:65:14: warning:
>> symbol '__nfit_test_ioremap' was not declared. Should it be static?
>>
>> This symbol is not used outside of security.c, so this
>
> s/security.c/iomap.c/
>
> Thanks,
> Santosh
>
>> commit marks it static.
>>
>> Reported-by: Hulk Robot <hulkci@huawei.com>
>> Signed-off-by: Zou Wei <zou_wei@huawei.com>
>> ---
>> tools/testing/nvdimm/test/iomap.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/tools/testing/nvdimm/test/iomap.c b/tools/testing/nvdimm/test/iomap.c
>> index c62d372..ed563bd 100644
>> --- a/tools/testing/nvdimm/test/iomap.c
>> +++ b/tools/testing/nvdimm/test/iomap.c
>> @@ -62,7 +62,7 @@ struct nfit_test_resource *get_nfit_res(resource_size_t resource)
>> }
>> EXPORT_SYMBOL(get_nfit_res);
>>
>> -void __iomem *__nfit_test_ioremap(resource_size_t offset, unsigned long size,
>> +static void __iomem *__nfit_test_ioremap(resource_size_t offset, unsigned long size,
>> void __iomem *(*fallback_fn)(resource_size_t, unsigned long))
>> {
>> struct nfit_test_resource *nfit_res = get_nfit_res(offset);
>> --
>> 2.6.2
>> _______________________________________________
>> Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org
>> To unsubscribe send an email to linux-nvdimm-leave@lists.01.org
> .
>
prev parent reply other threads:[~2021-04-20 7:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 7:10 Zou Wei
2021-04-20 6:35 ` Santosh Sivaraj
2021-04-20 7:19 ` Samuel Zou [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=066633f6-e624-54ef-0de0-5589305fdbe3@huawei.com \
--to=zou_wei@huawei.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=ira.weiny@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=santosh@fossix.org \
--cc=vishal.l.verma@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
all inboxes | Powered by JetHome®