netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Giant Sand Fan's" <rampxxxx@gmail.com>
To: "Patrick McHardy" <kaber@trash.net>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: NF_IP_PRE_ROUTING,... not defined
Date: Tue, 11 Nov 2008 10:00:10 +0100	[thread overview]
Message-ID: <417f50830811110100y2aae8e3ej99426153c6412fb0@mail.gmail.com> (raw)
In-Reply-To: <4918792A.2070309@trash.net>

ok, thanks, added by hand.

In my aim to port my netfilt-routing soft from 2.6.22 to 2.6.25 i have
too a problem, my *skb pointers are null (skb seems ok) and i don't
know if there is more related to thoses changes to 2.6.25 as define
__KERNEL__ thing in netfilter_ipv4.h any clue,idea, doc about those
complete changes.

2008/11/10 Patrick McHardy <kaber@trash.net>:
> Giant Sand Fan's wrote:
>>
>> because the #ifndef __KERNEL__ tags goes beyond NT_IP_PRE_ROUTING,..
>> defines , this change appears in 2.6.25 (because I works in 2.6.22)
>> and I cannot compile my kernel module hook with that version.
>>
>> There is a way to do a correct development-compilation with this headers?
>>
>> I cannot find anything about this issue.Yes I can move the "#endif"
>> but i think that must not be right thing.
>>
>> So sorry if I'm out of scope.
>
> The kernel doesn't need these definitions anymore, so they're not
> available to avoid people using them.
>
> For external modules that need to compile with multiple version,
> you can either add the necessary definitions yourself (the values
> are part of the ABI and unchangable) or possibly use the compat
> headers from xtables-addons.
>



-- 
Please avoid sending me Word or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html

  reply	other threads:[~2008-11-11  9:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-10 17:53 NF_IP_PRE_ROUTING,... not defined Giant Sand Fan's
2008-11-10 18:10 ` Patrick McHardy
2008-11-11  9:00   ` Giant Sand Fan's [this message]
2008-11-25 18:11     ` Giant Sand Fan's

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=417f50830811110100y2aae8e3ej99426153c6412fb0@mail.gmail.com \
    --to=rampxxxx@gmail.com \
    --cc=kaber@trash.net \
    --cc=netfilter-devel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).