netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: David Woodhouse <dwmw2@infradead.org>,
	netdev@vger.kernel.org, Jan Engelhardt <jengelh@computergmbh.de>,
	"David S. Miller" <davem@davemloft.net>,
	varekova@redhat.com, twoerner@redhat.com,
	Netfilter Development Mailinglist
	<netfilter-devel@vger.kernel.org>
Subject: Re: [NETFILTER]: Introduce nf_inet_address
Date: Fri, 22 Feb 2008 17:12:20 +0100	[thread overview]
Message-ID: <47BEF464.8060307@trash.net> (raw)
In-Reply-To: <47BEF36F.1020802@netfilter.org>

Pablo Neira Ayuso wrote:
> Patrick McHardy wrote:
>> Pablo Neira Ayuso wrote:
>>> Patrick McHardy wrote:
>>>> Yes, that was a bug in the lastest release. We need to
>>>> release a 1.4.1 version or something like that, but I'm
>>>> not too familiar with the release process, so I haven't
>>>> done this so far.
>>> I can schedule one for this weekend, just send me an ACK.
>>
>> That would be great. I think we had another issue in 1.4.0 with
>> some header files, but I can't remeber the details.
>>
>> Jan, I recall we talked about this some time ago, do you remember?
> 
> Was it related with kernel 2.4.x compilation?


Yes, I just found the old mail, the error was:

In file included from include/linux/netfilter/nf_nat.h:4,
                  from extensions/libipt_DNAT.c:9:
include/linux/netfilter/nf_conntrack_tuple.h:29: error: syntax error 
before "__be32"



  reply	other threads:[~2008-02-22 16:12 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200801291316.m0TDGivY024953@hera.kernel.org>
2008-02-19 13:49 ` [NETFILTER]: Introduce nf_inet_address David Woodhouse
2008-02-19 14:01   ` Patrick McHardy
2008-02-19 14:30     ` David Woodhouse
2008-02-19 14:45       ` Patrick McHardy
2008-02-20 10:24         ` Jan Engelhardt
2008-02-21 11:52         ` David Woodhouse
2008-02-21 12:00           ` Patrick McHardy
2008-02-21 12:19             ` David Woodhouse
2008-02-22  7:52         ` David Woodhouse
2008-02-22  8:01           ` David Woodhouse
2008-02-22 14:59             ` Patrick McHardy
2008-02-22 14:58           ` Patrick McHardy
2008-02-22 15:38             ` Pablo Neira Ayuso
2008-02-22 15:44               ` Patrick McHardy
2008-02-22 16:03                 ` Jan Engelhardt
2008-02-22 16:08                 ` Pablo Neira Ayuso
2008-02-22 16:12                   ` Patrick McHardy [this message]
2008-02-22 22:37                 ` David Woodhouse
2008-02-25 12:12                   ` Patrick McHardy
2008-02-25 12:17                     ` David Woodhouse
2008-02-25 12:20                       ` Patrick McHardy
2008-02-25 12:21                         ` David Woodhouse
2008-02-25 12:23                           ` Patrick McHardy
2008-02-25 12:29                             ` David Woodhouse

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=47BEF464.8060307@trash.net \
    --to=kaber@trash.net \
    --cc=davem@davemloft.net \
    --cc=dwmw2@infradead.org \
    --cc=jengelh@computergmbh.de \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.org \
    --cc=twoerner@redhat.com \
    --cc=varekova@redhat.com \
    /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;
as well as URLs for NNTP newsgroup(s).