From: Andrew Morton <akpm@linux-foundation.org>
To: linux-ia64@vger.kernel.org
Subject: Re: git-nfsd on ia64
Date: Sat, 16 Feb 2008 06:43:19 +0000 [thread overview]
Message-ID: <20080215224319.870e4921.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080215223943.d12b8eb5.akpm@linux-foundation.org>
On Fri, 15 Feb 2008 22:39:43 -0800 Andrew Morton <akpm@linux-foundation.org> wrote:
> Cunningly, current git-nfsd causes this, with ia64 allmodconfig:
>
> .config:3397:warning: trying to assign nonexistent symbol NFSD_TCP
> In file included from arch/ia64/ia32/sys_ia32.c:59:
> arch/ia64/ia32/ia32priv.h:297:1: warning: "elf_check_arch" redefined
> In file included from include/linux/elf.h:7,
> from include/linux/module.h:14,
> from include/linux/textsearch.h:9,
> from include/linux/skbuff.h:26,
> from include/linux/icmpv6.h:79,
> from include/linux/ipv6.h:197,
> from include/net/ipv6.h:18,
> from include/linux/sunrpc/svcauth.h:18,
> from include/linux/sunrpc/svc.h:18,
> from arch/ia64/ia32/sys_ia32.c:37:
> include/asm/elf.h:19:1: warning: this is the location of the previous definition
Easy fix:
--- a/include/linux/sunrpc/svcauth.h~git-nfsd-fix
+++ a/include/linux/sunrpc/svcauth.h
@@ -15,7 +15,6 @@
#include <linux/sunrpc/msg_prot.h>
#include <linux/sunrpc/cache.h>
#include <linux/hash.h>
-#include <net/ipv6.h>
#define SVC_CRED_NGROUPS 32
struct svc_cred {
@@ -25,6 +24,7 @@ struct svc_cred {
};
struct svc_rqst; /* forward decl */
+struct in6_addr;
/* Authentication is done in the context of a domain.
*
_
This should have been done in the first place, IMO. Avoid header file
dependencies, faster compile, avoid crap like the above.
next prev parent reply other threads:[~2008-02-16 6:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-16 6:39 git-nfsd on ia64 Andrew Morton
2008-02-16 6:43 ` Andrew Morton [this message]
2008-02-17 1:12 ` J. Bruce Fields
2008-02-17 1:18 ` Andrew Morton
2008-02-17 1:27 ` J. Bruce Fields
2008-02-17 13:13 ` Christoph Hellwig
2008-02-17 13:21 ` Christoph Hellwig
2008-02-17 14:08 ` Matthew Wilcox
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=20080215224319.870e4921.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-ia64@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