From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "David S. Miller" <davem@davemloft.net>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: linux-next: net tree build warnings
Date: Wed, 14 Oct 2009 15:20:00 +1100 [thread overview]
Message-ID: <20091014152000.15312908.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1365 bytes --]
Hi Dave,
Today's linux-next build (powerpc ppc44x_defconfig) produced these
warnings:
In file included from net/socket.c:94:
include/net/compat.h:45: warning: 'struct compat_mmsghdr' declared inside parameter list
include/net/compat.h:45: warning: its scope is only this definition or declaration, which is probably not what you want
In file included from net/core/scm.c:36:
include/net/compat.h:45: warning: 'struct compat_mmsghdr' declared inside parameter list
include/net/compat.h:45: warning: its scope is only this definition or declaration, which is probably not what you want
In file included from net/ipv4/ip_sockglue.c:37:
include/net/compat.h:45: warning: 'struct compat_mmsghdr' declared inside parameter list
include/net/compat.h:45: warning: its scope is only this definition or declaration, which is probably not what you want
In file included from net/ipv6/ipv6_sockglue.c:53:
include/net/compat.h:45: warning: 'struct compat_mmsghdr' declared inside parameter list
include/net/compat.h:45: warning: its scope is only this definition or declaration, which is probably not what you want
CONFIG_COMPAT is not set.
Caused by commit a2e2725541fad72416326798c2d7fa4dafb7d337 ("net:
Introduce recvmmsg socket syscall").
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2009-10-14 4:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-14 4:20 Stephen Rothwell [this message]
2009-10-14 4:34 ` linux-next: net tree build warnings Stephen Rothwell
2009-10-14 22:11 ` David Miller
2009-10-15 1:55 ` Arnaldo Carvalho de Melo
2009-10-17 2:10 ` [PATCH 1/1] " Arnaldo Carvalho de Melo
2009-10-20 8:09 ` David Miller
2009-10-20 8:14 ` Stephen Rothwell
2009-10-20 8:18 ` David Miller
2009-10-20 8:22 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2009-09-04 4:34 Stephen Rothwell
2009-09-04 4:35 ` David Miller
2009-06-11 4:55 Stephen Rothwell
2009-06-11 6:47 ` David Miller
2009-06-11 7:20 ` Stephen Rothwell
2009-04-29 4:59 Stephen Rothwell
2009-04-29 6:02 ` David Miller
2009-04-30 0:54 ` David Miller
2009-04-30 7:06 ` Stephen Rothwell
2009-03-26 6:37 Stephen Rothwell
2009-03-26 7:50 ` Eric Leblond
2009-03-26 13:17 ` Patrick McHardy
2009-03-26 22:01 ` Stephen Rothwell
2009-03-16 6:03 Stephen Rothwell
2009-03-16 6:05 ` Dhananjay Phadke
2008-12-17 7:22 Stephen Rothwell
2008-12-17 7:53 ` David Miller
2008-12-17 8:04 ` Eilon Greenstein
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=20091014152000.15312908.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=acme@redhat.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.