From mboxrd@z Thu Jan 1 00:00:00 1970 From: Patrick McHardy Subject: Re: concerning p-o-m fixes for 2.6.17 API change Date: Sat, 24 Jun 2006 14:26:17 +0200 Message-ID: <449D2F69.5090909@trash.net> References: <1151096311.3421.10.camel@murdegern.hindenburgdamm.example> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Cc: netfilter-devel@lists.netfilter.org Return-path: To: Torsten Luettgert In-Reply-To: <1151096311.3421.10.camel@murdegern.hindenburgdamm.example> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: netfilter-devel-bounces@lists.netfilter.org Errors-To: netfilter-devel-bounces@lists.netfilter.org List-Id: netfilter-devel.vger.kernel.org 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.