From: Paul Moore <pmoore@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
James Morris <jmorris@namei.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Casey Schaufler <casey@schaufler-ca.com>
Subject: Re: linux-next: build warning after merge of the security tree
Date: Tue, 05 Aug 2014 15:49:17 -0400 [thread overview]
Message-ID: <2473453.7vHnsXcYFU@sifl> (raw)
In-Reply-To: <20140804162549.28c9889d@canb.auug.org.au>
On Monday, August 04, 2014 04:25:49 PM Stephen Rothwell wrote:
> Hi James,
>
> After merging the security tree, today's linux-next build (powerpc
> ppc64_defconfig) produced this warning:
>
> In file included from include/net/cipso_ipv4.h:41:0,
> from net/ipv4/sysctl_net_ipv4.c:24:
> include/net/netlabel.h:527:12: warning: 'netlbl_catmap_setlong' defined but
> not used [-Wunused-function] static int netlbl_catmap_setlong(struct
> netlbl_lsm_catmap **catmap, ^
>
> Introduced by commit 4b8feff251da ("netlabel: fix the horribly broken
> catmap functions").
Looks like I forgot to mark the dummy function as an inline, I'll get that
fixed soon.
--
paul moore
security and virtualization @ redhat
next prev parent reply other threads:[~2014-08-05 19:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-04 6:25 linux-next: build warning after merge of the security tree Stephen Rothwell
2014-08-05 19:49 ` Paul Moore [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-08-12 5:04 Stephen Rothwell
2012-04-23 6:56 Stephen Rothwell
2012-04-23 15:23 ` Kees Cook
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=2473453.7vHnsXcYFU@sifl \
--to=pmoore@redhat.com \
--cc=casey@schaufler-ca.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).