From: Alex Shi <alex.shi@linux.alibaba.com>
To: unlisted-recipients:; (no To-header on input)
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
Chuck Lever <chuck.lever@oracle.com>,
linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fs/nfsd: remove unused NFSDDBG_FACILITY to tame gcc
Date: Fri, 6 Nov 2020 16:05:28 +0800 [thread overview]
Message-ID: <8145bb50-8606-809d-01b2-221a6c259103@linux.alibaba.com> (raw)
In-Reply-To: <1604634457-3954-2-git-send-email-alex.shi@linux.alibaba.com>
Sorry, gcc is error on this case, it cann't find out much of
NFSDDBG_##flag
Forget this patch.
Alex
在 2020/11/6 上午11:47, Alex Shi 写道:
> There are lots of NFSDDBG_FACILITY defined in many files
> but it isn't used anywhere. so remove it to tame the gcc warning:
>
> fs/nfsd/nfsxdr.c:12:0: warning: macro "NFSDDBG_FACILITY" is not used
> [-Wunused-macros]
> fs/nfsd/filecache.c:23:0: warning: macro "NFSDDBG_FACILITY" is not used
> [-Wunused-macros]
> fs/nfsd/nfs3xdr.c:17:0: warning: macro "NFSDDBG_FACILITY" is not used
> [-Wunused-macros]
> fs/nfsd/flexfilelayoutxdr.c:11:0: warning: macro "NFSDDBG_FACILITY" is
> not used [-Wunused-macros]
> fs/nfsd/nfsxdr.c:12:0: warning: macro "NFSDDBG_FACILITY" is not used
> [-Wunused-macros]
> fs/nfsd/filecache.c:23:0: warning: macro "NFSDDBG_FACILITY" is not used
> [-Wunused-macros]
> fs/nfsd/nfs3xdr.c:17:0: warning: macro "NFSDDBG_FACILITY" is not used
> [-Wunused-macros]
> fs/nfsd/flexfilelayoutxdr.c:11:0: warning: macro "NFSDDBG_FACILITY" is
> not used [-Wunused-macros]
>
next prev parent reply other threads:[~2020-11-06 8:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1604634457-3954-1-git-send-email-alex.shi@linux.alibaba.com>
2020-11-06 3:47 ` [PATCH] fs/nfsd: remove unused NFSDDBG_FACILITY to tame gcc Alex Shi
2020-11-06 8:05 ` Alex Shi [this message]
2020-11-10 20:55 ` kernel test robot
2020-11-11 5:35 ` Alex Shi
2020-11-11 5:52 ` [kbuild-all] " Philip Li
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=8145bb50-8606-809d-01b2-221a6c259103@linux.alibaba.com \
--to=alex.shi@linux.alibaba.com \
--cc=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@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