All of lore.kernel.org
 help / color / mirror / Atom feed
From: jamal <hadi@cyberus.ca>
To: Andreas Henriksson <andreas@fatal.se>
Cc: shemminger@vyatta.com, netdev@vger.kernel.org
Subject: Re: [PATCH 0/3] iproute: fix tc ipt/xt module.
Date: Thu, 03 Dec 2009 08:09:38 -0500	[thread overview]
Message-ID: <1259845778.3766.32.camel@bigi> (raw)
In-Reply-To: <cover.1259765732.git.andreas@fatal.se>


On Wed, 2009-12-02 at 16:10 +0100, Andreas Henriksson wrote:
> The xtables API has changed since the tc xt module was written.
> This mini-series moves the legacy stuff out of the way (kept for
> compatibility with older iptables versions) and starts
> a new fresh xt module.
> 
> Hopefully the xtables api will be kept stable in the future.
> If so, this new xt module should continue working since it only
> uses exposed functions (unlike the old one which had an internal
> header to access internal functions in xtables).
> 
> Andreas Henriksson (3):
>   Keep the old tc/ipt/xt module for compatibility.
>   Add new (iptables 1.4.5 compatible) tc/ipt/xt module.
>   Slightly improve the configure script.

Signed-off-by: Jamal Hadi Salim <hadi@cyberus.ca>

Andreas, in the future can you CC me please - I dont read netdev
in real time (sometimes i catch up in a month and skim over).

cheers,
jamal


  parent reply	other threads:[~2009-12-03 13:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-02 15:10 [PATCH 0/3] iproute: fix tc ipt/xt module Andreas Henriksson
2009-12-02 15:11 ` [PATCH 1/3] Keep the old tc/ipt/xt module for compatibility Andreas Henriksson
2009-12-02 15:11 ` [PATCH 2/3] Add new (iptables 1.4.5 compatible) tc/ipt/xt module Andreas Henriksson
2009-12-02 16:58   ` Stephen Hemminger
2009-12-02 17:12     ` Andreas Henriksson
2009-12-02 15:12 ` [PATCH 3/3] Slightly improve the configure script Andreas Henriksson
2009-12-03 13:09 ` jamal [this message]
2009-12-03 15:44   ` [PATCH 0/3] iproute: fix tc ipt/xt module Andreas Henriksson
2009-12-26 19:18   ` Stephen Hemminger

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=1259845778.3766.32.camel@bigi \
    --to=hadi@cyberus.ca \
    --cc=andreas@fatal.se \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@vyatta.com \
    /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.