public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: zhong jiang <zhongjiang@huawei.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: <georgi.djakov@linaro.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] interconnect: Fix a GCC compiler warning
Date: Mon, 17 Sep 2018 17:19:18 +0800	[thread overview]
Message-ID: <5B9F7196.1070203@huawei.com> (raw)
In-Reply-To: <20180917085954.GA23740@kroah.com>

On 2018/9/17 16:59, Greg KH wrote:
> On Mon, Sep 17, 2018 at 04:53:31PM +0800, zhong jiang wrote:
>> +to Greg and Andrew.
>>
>> On 2018/9/16 22:31, zhong jiang wrote:
>>> Fix the following compile warning:
>>>
>>> drivers/interconnect/core.c:26:23: warning: 'icc_debugfs_dir' defined but not used [-Wunused-variable]
>>>  static struct dentry *icc_debugfs_dir;
>>>
>>> Signed-off-by: zhong jiang <zhongjiang@huawei.com>
>>> ---
>>>  drivers/interconnect/core.c | 3 +++
> This file is not in a released tree, where are you seeing it?
I see it in linux-next.
>>>  1 file changed, 3 insertions(+)
>>>
>>> diff --git a/drivers/interconnect/core.c b/drivers/interconnect/core.c
>>> index 2740f1a..9ea9959 100644
>>> --- a/drivers/interconnect/core.c
>>> +++ b/drivers/interconnect/core.c
>>> @@ -23,7 +23,10 @@
>>>  static DEFINE_IDR(icc_idr);
>>>  static LIST_HEAD(icc_provider_list);
>>>  static DEFINE_MUTEX(icc_lock);
>>> +
>>> +#ifdef CONFIG_DEBUG_FS
>>>  static struct dentry *icc_debugfs_dir;
>>> +#endif
> Why not move the variable to where it is used?  It should be able to go
> under an existing #ifdef section, right?
Because the variable need to be used in __init and __exit.  So it should be identified as
a gloabl variable.  I fix it under the #ifdef condition.

Thanks,
zhong jiang
> thanks,
>
> greg k-h
>
> .
>



  reply	other threads:[~2018-09-17  9:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-16 14:31 [PATCH] interconnect: Fix a GCC compiler warning zhong jiang
2018-09-17  6:15 ` zhong jiang
2018-09-17  6:54   ` Greg KH
2018-09-17  7:15     ` zhong jiang
2018-09-17  8:48       ` Greg KH
2018-09-17  8:56         ` zhong jiang
2018-09-17  8:53 ` zhong jiang
2018-09-17  8:59   ` Greg KH
2018-09-17  9:19     ` zhong jiang [this message]
2018-09-17  9:24       ` Greg KH
2018-09-17 10:38         ` Georgi Djakov

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=5B9F7196.1070203@huawei.com \
    --to=zhongjiang@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=georgi.djakov@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --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