From: Andrew Morton <akpm@digeo.com>
To: Helge Hafting <helgehaf@aitel.hist.no>
Cc: linux-kernel@vger.kernel.org, "David S. Miller" <davem@redhat.com>
Subject: Re: 2.5.59-mm8 compile error in tcp_ipv6.c
Date: Tue, 4 Feb 2003 01:21:05 -0800 [thread overview]
Message-ID: <20030204012105.4249b053.akpm@digeo.com> (raw)
In-Reply-To: <3E3F857A.5C55A6E3@aitel.hist.no>
Helge Hafting <helgehaf@aitel.hist.no> wrote:
>
> mm8 gave me this error. mm6 didn't have this problem. _I haven't
> looked at mm7.
>
> gcc -Wp,-MD,net/ipv6/.tcp_ipv6.o.d -D__KERNEL__ -Iinclude -Wall
> -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
> -pipe -mpreferred-stack-boundary=2 -march=i686
> -Iinclude/asm-i386/mach-default -fomit-frame-pointer -nostdinc
> -iwithprefix include -DKBUILD_BASENAME=tcp_ipv6 -DKBUILD_MODNAME=ipv6
> -c -o net/ipv6/tcp_ipv6.o net/ipv6/tcp_ipv6.c
> net/ipv6/tcp_ipv6.c:1750: conflicting types for `tcp_v6_xmit'
> net/ipv6/tcp_ipv6.c:63: previous declaration of `tcp_v6_xmit'
Somebody's finger slipped.
diff -puN net/ipv6/tcp_ipv6.c~a net/ipv6/tcp_ipv6.c
--- 25/net/ipv6/tcp_ipv6.c~a 2003-02-04 01:20:17.000000000 -0800
+++ 25-akpm/net/ipv6/tcp_ipv6.c 2003-02-04 01:20:19.000000000 -0800
@@ -60,7 +60,7 @@ static void tcp_v6_send_check(struct soc
struct sk_buff *skb);
static int tcp_v6_do_rcv(struct sock *sk, struct sk_buff *skb);
-static int tcp_v6_xmit(struct sk_buff *skb);
+static int tcp_v6_xmit(struct sk_buff *skb, int ipfragok)
static struct tcp_func ipv6_mapped;
static struct tcp_func ipv6_specific;
_
next prev parent reply other threads:[~2003-02-04 9:11 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-04 7:31 2.5.59-mm8 Andrew Morton
2003-02-04 8:02 ` 2.5.59-mm8 Joshua Kwan
2003-02-04 8:05 ` 2.5.59-mm8 Andrew Morton
2003-02-04 8:08 ` 2.5.59-mm8 Joshua Kwan
2003-02-04 8:09 ` 2.5.59-mm8 Martin J. Bligh
2003-02-04 8:17 ` 2.5.59-mm8 Andrew Morton
2003-02-04 22:15 ` Broken SCSI code in the BK tree (was: 2.5.59-mm8) Martin J. Bligh
2003-02-06 5:13 ` Martin J. Bligh
2003-02-06 20:50 ` Martin J. Bligh
2003-02-06 22:30 ` Martin J. Bligh
2003-02-06 23:25 ` James Bottomley
2003-02-07 1:24 ` Patrick Mansfield
2003-02-07 2:01 ` Martin J. Bligh
2003-02-07 2:25 ` Patrick Mansfield
2003-02-07 4:05 ` Doug Ledford
2003-02-07 4:19 ` Anton Blanchard
2003-02-07 8:50 ` Mike Anderson
2003-02-07 4:19 ` Andrew Morton
2003-02-07 4:24 ` Doug Ledford
2003-02-07 4:35 ` William Lee Irwin III
2003-02-07 4:53 ` Matthew Jacob
2003-02-07 4:50 ` Matthew Jacob
2003-02-07 4:28 ` Martin J. Bligh
2003-02-04 9:07 ` 2.5.59-mm8 Dave Hansen
2003-02-04 9:18 ` 2.5.59-mm8 compile error in tcp_ipv6.c Helge Hafting
2003-02-04 9:21 ` Andrew Morton [this message]
2003-02-04 9:29 ` David S. Miller
2003-02-04 9:33 ` 2.5.59-mm8 Arjan van de Ven
2003-02-05 8:08 ` 2.5.59-mm8 Mike Galbraith
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=20030204012105.4249b053.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=davem@redhat.com \
--cc=helgehaf@aitel.hist.no \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®