Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Harald Welte <laforge@netfilter.org>
To: "Gaël Le Mignot" <kilobug@freesurf.fr>
Cc: Netfilter Development Mailinglist
	<netfilter-devel@lists.netfilter.org>,
	Netfilter Mailinglist <netfilter@lists.netfilter.org>
Subject: Re: Call for testing: patch-o-matic-ng
Date: Tue, 23 Dec 2003 18:30:22 +0100	[thread overview]
Message-ID: <20031223173022.GA3879@obroa-skai.de.gnumonks.org> (raw)
In-Reply-To: <plopm3zndjoexg.fsf@drizzt.kilobug.org>

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

On Tue, Dec 23, 2003 at 02:13:15PM +0100, Gaël Le Mignot wrote:
> I've tested pom-ng on 2.6.0  with USAGI patch, the patch-o-matic seems
> to work, but the kernel doesn't compile (I put nearly all patches, and
> select M in the kernel config wherever it was possible):
> 
>   CC      net/core/netfilter.o
> net/core/netfilter.c: In function `nf_log_register':
> net/core/netfilter.c:760: warning: implicit declaration of function `br_write_lock_bh'
> net/core/netfilter.c:760: error: `BR_NETPROTO_LOCK' undeclared (first use in this function)
> net/core/netfilter.c:760: error: (Each undeclared identifier is reported only once
> net/core/netfilter.c:760: error: for each function it appears in.)
> net/core/netfilter.c:765: warning: implicit declaration of function `br_write_unlock_bh'
> net/core/netfilter.c: In function `nf_log_unregister':
> net/core/netfilter.c:770: error: `BR_NETPROTO_LOCK' undeclared (first use in this function)
> make[3]: *** [net/core/netfilter.o] Error 1
> 
> 
> I think maybe some patches doesn't work with 2.6, would it possible to
> add a way to select patch that works with 2.6 ? like ./runme extra-2.6
> or such ?

yes, indeed.  There are numerous patches that would not work in the
2.6.x kernels.  They have yet to be identified.  Once they are
identified, we can put a special "requires" tag into the 'info' file of
those patches.

This way the 2.4 only patches would only be offered if you have a 2.4.x
kernel source (and vice-versa).

You could help us in finding out which patches compile and which ones
don't.

> -- 
> Gael Le Mignot "Kilobug" - kilobug@nerim.net - http://kilobug.free.fr

-- 
- Harald Welte <laforge@netfilter.org>             http://www.netfilter.org/
============================================================================
  "Fragmentation is like classful addressing -- an interesting early
   architectural error that shows how much experimentation was going
   on while IP was being designed."                    -- Paul Vixie

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

  reply	other threads:[~2003-12-23 17:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-21 12:24 Call for testing: patch-o-matic-ng Harald Welte
2003-12-22  9:56 ` KOVACS Krisztian
2003-12-22 12:00   ` Harald Welte
2003-12-23 13:13 ` Gaël Le Mignot
2003-12-23 17:30   ` Harald Welte [this message]
2003-12-23 18:56     ` Unknown, Alistair Tonner
2003-12-24  0:26     ` Gaël Le Mignot
2003-12-24  1:03       ` Unknown, Alistair Tonner
     [not found]     ` <200312231356.17135.Alistair Tonner <>
     [not found]       ` <200312231356.17135.AlistairTonner<>
2003-12-25  9:06         ` Galtar
2003-12-25  9:41           ` Antony Stone
2004-01-22 15:57 ` ip_conntrack_pptp Jan Kaastrup
2004-01-22 17:53   ` ip_conntrack_pptp Harald Welte
2004-01-22 18:09     ` ip_conntrack_pptp Unknown, Alistair Tonner
2004-01-22 18:09     ` ip_conntrack_pptp Unknown, Alistair Tonner
2004-01-22 18:09     ` ip_conntrack_pptp Unknown, Alistair Tonner
2004-01-22 19:41     ` ip_conntrack_pptp Arnt Karlsen
     [not found]     ` <000d01c3e3ed$9875b0f0$2d64a8c0@pcjka>
2004-01-26 16:19       ` ip_conntrack_pptp Harald Welte
  -- strict thread matches above, loose matches on Subject: below --
2003-12-24  2:30 Call for testing: patch-o-matic-ng Vilmos Branyik

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=20031223173022.GA3879@obroa-skai.de.gnumonks.org \
    --to=laforge@netfilter.org \
    --cc=kilobug@freesurf.fr \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=netfilter@lists.netfilter.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