From: Patrick McHardy <kaber@trash.net>
To: Torsten Luettgert <t.luettgert@pressestimmen.de>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: concerning p-o-m fixes for 2.6.17 API change
Date: Sat, 24 Jun 2006 14:26:17 +0200 [thread overview]
Message-ID: <449D2F69.5090909@trash.net> (raw)
In-Reply-To: <1151096311.3421.10.camel@murdegern.hindenburgdamm.example>
Torsten Luettgert wrote:
> Hi list,
>
> I noticed the match/target API changed a bit in 2.6.17,
> so a bunch of code in patch-o-matic-ng needs updates.
> I fixed ipp2p, ROUTE, time, and u32 (it's quite trivial).
>
> I'd like to submit the patches (and thus work against the
> "bit-rot" we all hate). Problem is, they are quite clumsy -
> the correct way IMHO is to copy the latest kernel directory
> (normally linux-2.6/) to linux-2.6.17 and then fix that,
> so 2.6.16 and older kernels still work, too. So you can't
> see what is happening in the patches, they just create 99%
> identical copies of the old files.
>
> Patrick, I guess you're the one to ask - would you like
> those patches, and in what format?
Sure, just send them along as normal diffs. But please no new
directories, we decided to keep only a single version of things
in pomng that runs with the latest kernel.
next prev parent reply other threads:[~2006-06-24 12:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-23 20:58 concerning p-o-m fixes for 2.6.17 API change Torsten Luettgert
2006-06-24 7:13 ` Krzysztof Oledzki
2006-06-24 13:51 ` [PATCH] 2.6.17 API changes for ipp2p, time Torsten Luettgert
2006-06-24 12:26 ` Patrick McHardy [this message]
2006-06-24 13:51 ` [PATCH] 2.6.17 API changes for ROUTE, u32, set Torsten Luettgert
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=449D2F69.5090909@trash.net \
--to=kaber@trash.net \
--cc=netfilter-devel@lists.netfilter.org \
--cc=t.luettgert@pressestimmen.de \
/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.