netfilter.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mr Dash Four <mr.dash.four@googlemail.com>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: "netfilter@vger.kernel.org" <netfilter@vger.kernel.org>
Subject: Re: ipset maximal/minimal revision conflict
Date: Tue, 26 Apr 2011 16:06:14 +0100	[thread overview]
Message-ID: <4DB6DF66.6040009@googlemail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1104261558430.1834@blackhole.kfki.hu>


> The hash:*port* types have got a new revision due to the introduced SCTP 
> and UDPLITE support. The ipset package contains the matching kernel 
> modules, the kernel tree is a little bit behind.
>   
I see, the ipset files in the kernel version and the kernel files in the 
ipset package are out of sync then, right?

Would I be able to successfully split this up by using the source files 
in the kernel/ directory of the ipset 6.4 package and move them over to 
the ipset kernel source directory, whilst keeping all the 
make/configuration files in the ipset kernel directory (Kbuild and 
alike) intact?

Would that solve the above problem (keeping/building the ipset package 
as a whole is *not* an option for me, before you ask)? I also assume 
that the kernel files in the ipset package are newer as the above error 
suggests, right?


  reply	other threads:[~2011-04-26 15:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-26 11:16 ipset maximal/minimal revision conflict Mr Dash Four
2011-04-26 14:05 ` Jozsef Kadlecsik
2011-04-26 15:06   ` Mr Dash Four [this message]
2011-04-26 18:11     ` Jozsef Kadlecsik
2011-04-26 19:25       ` Mr Dash Four

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=4DB6DF66.6040009@googlemail.com \
    --to=mr.dash.four@googlemail.com \
    --cc=kadlec@blackhole.kfki.hu \
    --cc=netfilter@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).