From: Martijn Lievaart <netfilter-devel@rtij.nl>
To: Netfilter Developers List <netfilter-devel@lists.netfilter.org>
Subject: I don't understand what goes where, very confused about POM-ng
Date: Wed, 05 May 2004 19:14:52 +0200 [thread overview]
Message-ID: <4099210C.40309@rtij.nl> (raw)
Hi,
Using CVS of today 5/5/2004.
I'm trying to port the psd match to 2.6. The C code is ready (not much
of a change needed). However POM will not apply the headerfile from the
linux/ tree, I need to copy it to the linux-2.6 tree. I would expect
that everything in the linux tree would also be applied, eventually
overridden by something in the linux-2.6 tree. Why else have seperate
linux-2.4 trees?
By now I gather that POM-ng tries to find a best match, and does this
independently for the ladds and the files (and the patches as well?). I
find this very confusing, but I think this is by design?
Anyhow, I looked at a couple of other patches and many have their header
file only in the linux-tree. Many are also base, so probably already
applied to any 2.6 kernel, but the why have a linux-2.6 tree in that
case? One patch where this really breaks is the XOR patch, it does not
apply to 2.6 because POM-ng does not copy the header.
As an alternative, would it be possible to just create a linux-2.6.patch
file that applies after the 2.4 patch has applied? This would be a good
solution because many patches need only minor modifications to newly
added files (especially only ipt_xxx.c) to make them run under 2.6.
TIA,
Martijn Lievaart
next reply other threads:[~2004-05-05 17:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-05 17:14 Martijn Lievaart [this message]
2004-05-05 18:00 ` I don't understand what goes where, very confused about POM-ng Martijn Lievaart
2004-05-05 18:33 ` Jozsef Kadlecsik
2004-05-05 19:28 ` Martijn Lievaart
2004-05-05 21:19 ` Jozsef Kadlecsik
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=4099210C.40309@rtij.nl \
--to=netfilter-devel@rtij.nl \
--cc=netfilter-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.