All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: johnpol@2ka.mipt.ru
Cc: Harald Welte <laforge@netfilter.org>,
	netfilter-devel@lists.netfilter.org
Subject: Re: [1/1] OSF: pom-ng - linux-2.6.
Date: Wed, 08 Dec 2004 19:44:42 +0100	[thread overview]
Message-ID: <41B74B9A.8090609@trash.net> (raw)
In-Reply-To: <1102503533.3363.48.camel@uganda>

Evgeniy Polyakov wrote:

>Since OSF originally was created in 2.5 environment 
>it is strange not to have 2.6 support for OSF.
>This(similar) patch was sent some time ago but was lost.
>Please apply.
>  
>
Please send patches that apply -p1 in the patch-o-matic-ng directory
in the future. Your patch doesn't apply at all:

~/src/nf/svn/netfilter/trunk/patch-o-matic-ng/osf/linux-2.6/net/ipv4/netfilter$ 
patch -p6 </tmp/ipt_osf --dry-run
missing header for unified diff at line 3 of patch
(Stripping trailing CRs from patch.)
patching file ipt_osf.c
Hunk #1 succeeded at 52 with fuzz 2.
Hunk #2 FAILED at 77.
Hunk #3 FAILED at 154.
Hunk #4 FAILED at 185.
Hunk #5 FAILED at 414.
Hunk #6 FAILED at 603.
Hunk #7 FAILED at 616.
Hunk #8 FAILED at 636.
Hunk #9 FAILED at 855.
8 out of 9 hunks FAILED -- saving rejects to file ipt_osf.c.rej

To make osf fit for 2.6, you also need to handle non-linear skbs.

Regards
Patrick

      parent reply	other threads:[~2004-12-08 18:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-08 10:58 [1/1] OSF: pom-ng - linux-2.6 Evgeniy Polyakov
2004-12-08 11:02 ` Evgeniy Polyakov
2004-12-08 18:48   ` Patrick McHardy
2004-12-12 15:13     ` Evgeniy Polyakov
2005-01-02 23:31       ` Patrick McHardy
2004-12-08 13:32 ` Pavel A. Nekrasov
2004-12-08 13:43   ` Evgeniy Polyakov
2004-12-08 18:44 ` Patrick McHardy [this message]

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=41B74B9A.8090609@trash.net \
    --to=kaber@trash.net \
    --cc=johnpol@2ka.mipt.ru \
    --cc=laforge@netfilter.org \
    --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.