From: Greg KH <gregkh@linuxfoundation.org>
To: zhong jiang <zhongjiang@huawei.com>
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 11:24:29 +0200 [thread overview]
Message-ID: <20180917092429.GB25662@kroah.com> (raw)
In-Reply-To: <5B9F7196.1070203@huawei.com>
On Mon, Sep 17, 2018 at 05:19:18PM +0800, zhong jiang wrote:
> 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.
Then please contact the owner of the branch where it came from. They
are the only ones that can handle such a patch, not anyone else.
> >>> 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.
If the variable is being used this way, then the code is written
incorrectly, such an #ifdef should not be needed for any debugfs
calls/variables.
thanks,
greg k-h
next prev parent reply other threads:[~2018-09-17 9:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-16 14:31 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
2018-09-17 9:24 ` Greg KH [this message]
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=20180917092429.GB25662@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=georgi.djakov@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zhongjiang@huawei.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®