public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Udo A. Steinberg" <us15@os.inf.tu-dresden.de>
To: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.11-rc2
Date: Fri, 21 Jan 2005 22:32:47 -0800	[thread overview]
Message-ID: <20050121223247.65c544f8@laptop.hypervisor.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0501211806130.3053@ppc970.osdl.org>

[-- Attachment #1: Type: text/plain, Size: 1160 bytes --]

On Fri, 21 Jan 2005 18:13:55 -0800 (PST) Linus Torvalds (LT) wrote:

LT> Ok, trying to calm things down again for a 2.6.11 release.

Connection tracking does not compile...

 CC      net/ipv4/netfilter/ip_conntrack_standalone.o
In file included from net/ipv4/netfilter/ip_conntrack_standalone.c:34:
include/linux/netfilter_ipv4/ip_conntrack.h:135: warning: "struct ip_conntrack" declared inside parameter list
include/linux/netfilter_ipv4/ip_conntrack.h:135: warning: its scope is only this definition or declaration, which is probably not what you want
include/linux/netfilter_ipv4/ip_conntrack.h:305: warning: "enum ip_nat_manip_type" declared inside parameter list
include/linux/netfilter_ipv4/ip_conntrack.h:306: error: parameter `manip' has incomplete type
include/linux/netfilter_ipv4/ip_conntrack.h: In function `ip_nat_initialized':
include/linux/netfilter_ipv4/ip_conntrack.h:307: error: `IP_NAT_MANIP_SRC' undeclared (first use in this function)
include/linux/netfilter_ipv4/ip_conntrack.h:307: error: (Each undeclared identifier is reported only once
include/linux/netfilter_ipv4/ip_conntrack.h:307: error: for each function it appears in.)


-Udo.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-01-22  6:33 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-22  2:13 Linux 2.6.11-rc2 Linus Torvalds
2005-01-22  6:32 ` Udo A. Steinberg [this message]
2005-01-22 14:04   ` Martin Josefsson
2005-01-22 20:57     ` Udo A. Steinberg
2005-01-22 21:05       ` Martin Josefsson
2005-01-22 21:15       ` Linus Torvalds
2005-01-22 23:54     ` sean
2005-01-23  0:34       ` Martin Josefsson
2005-01-23 17:26         ` sean
2005-01-23 21:11 ` Magnus Määttä
2005-01-24 10:43   ` Adrian Bunk
2005-01-24 18:23     ` Magnus Määttä
2005-01-24 19:28 ` Linux 2.6.11-rc2 (compile stats) John Cherry
2005-01-25  0:41 ` Linux 2.6.11-rc2: vmnet breaks; put skb_copy_datagram back in place Sytse Wielinga
2005-01-25  7:33   ` Christoph Hellwig
  -- strict thread matches above, loose matches on Subject: below --
2005-01-24  6:51 Linux 2.6.11-rc2 David Brownell
2005-01-24 18:05 ` Martin Josefsson
2005-01-24 21:13   ` David Brownell
2005-01-25 18:35 ` David Ford
2005-01-25 18:54   ` David Brownell

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=20050121223247.65c544f8@laptop.hypervisor.org \
    --to=us15@os.inf.tu-dresden.de \
    --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