From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Paul Moore <paul.moore@hp•com>
Cc: linux-next@vger•kernel.org
Subject: linux-next: lblnet tree build warnings
Date: Fri, 13 Mar 2009 16:32:52 +1100 [thread overview]
Message-ID: <20090313163252.6333812e.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 782 bytes --]
Hi Paul,
Today's linux-next build (powerpc ppc64_defconfig) produced these
warnings:
In file included from net/ipv4/ip_options.c:26:
include/net/cipso_ipv4.h: In function 'cipso_v4_req_delattr':
include/net/cipso_ipv4.h:264: warning: 'return' with a value, in function returning void
In file included from net/ipv4/sysctl_net_ipv4.c:22:
include/net/cipso_ipv4.h: In function 'cipso_v4_req_delattr':
include/net/cipso_ipv4.h:264: warning: 'return' with a value, in function returning void
Caused by commit d584c27edca286826e9145a3158f03e3bc81a6c0 ("netlabel:
Label incoming TCP connections correctly in SELinux"). (BTW, that commit
has no Signed-off-by.)
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2009-03-13 5:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-13 5:32 Stephen Rothwell [this message]
2009-03-13 16:09 ` linux-next: lblnet tree build warnings Paul Moore
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=20090313163252.6333812e.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=paul.moore@hp$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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