From: Borislav Petkov <bp@alien8.de>
To: Alexandru Gheorghiu <gheorghiuandru@gmail.com>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
Patrick McHardy <kaber@trash.net>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: netfilter: nfnetlink: Fixed warning for nfnl_get_lock
Date: Mon, 4 Mar 2013 22:05:51 +0100 [thread overview]
Message-ID: <20130304210551.GA22306@pd.tnic> (raw)
In-Reply-To: <1362426192-2921-1-git-send-email-gheorghiuandru@gmail.com>
On Mon, Mar 04, 2013 at 09:43:11PM +0200, Alexandru Gheorghiu wrote:
> Removed unused function nfnl_get_lock which fixed the following warning:
> net/netfilter/nfnetlink.c:65:22: warning: ‘nfnl_get_lock’ defined but not used [-Wunused-function]
>
> Signed-off-by: Alexandru Gheorghiu <gheorghiuandru@gmail.com>
> ---
> net/netfilter/nfnetlink.c | 5 -----
> 1 file changed, 5 deletions(-)
>
> diff --git a/net/netfilter/nfnetlink.c b/net/netfilter/nfnetlink.c
> index d578ec2..44aa0a7 100644
> --- a/net/netfilter/nfnetlink.c
> +++ b/net/netfilter/nfnetlink.c
> @@ -62,11 +62,6 @@ void nfnl_unlock(__u8 subsys_id)
> }
> EXPORT_SYMBOL_GPL(nfnl_unlock);
>
> -static struct mutex *nfnl_get_lock(__u8 subsys_id)
> -{
> - return &table[subsys_id].mutex;
> -}
> -
I see the same warning here, gcc (Debian 4.7.2-5) 4.7.2.
Actually this function *is* used a bit further in the same file in
nfnetlink_rcv_msg().
But gcc complains for some reason of which I don't even have the
slightest idea. However, if you declare the above function "static
inline..." the warning is gone.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2013-03-04 21:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 19:43 [PATCH] net: netfilter: nfnetlink: Fixed warning for nfnl_get_lock Alexandru Gheorghiu
2013-03-04 21:05 ` Borislav Petkov [this message]
2013-03-04 21:23 ` Pablo Neira Ayuso
2013-03-04 21:42 ` Borislav Petkov
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=20130304210551.GA22306@pd.tnic \
--to=bp@alien8.de \
--cc=davem@davemloft.net \
--cc=gheorghiuandru@gmail.com \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pablo@netfilter.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