From: Torsten Luettgert <t.luettgert@pressestimmen.de>
To: Patrick McHardy <kaber@trash.net>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: [PATCH] ip_nat_sip: fix compiler warning
Date: Sun, 28 May 2006 17:32:25 +0200 [thread overview]
Message-ID: <1148830346.32002.9.camel@scaramouche.combox.de> (raw)
In-Reply-To: <4479B3C4.1040404@trash.net>
On So, 2006-05-28 at 16:29 +0200, Patrick McHardy wrote:
> Torsten Luettgert wrote:
> >
> Thanks, but the SIP helper in patch-o-matic is quite out of date.
> I have a version with that warning (and some other things) already
> fixed queued for upstream submission. After that I'll most likely
> remove it from pom.
Ok, I'll just switch if off in my 2.6.16 kernels.
BTW: What about the new protoff argument to match functions, and
the change from struct ipt_ip * to void * in the checkentry
functions (e.g. in the set match).
Are those already fixed and going upstream, too, or would it be
worthwile to submit patches for old matches and targets?
Regards,
Torsten
next prev parent reply other threads:[~2006-05-28 15:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-28 13:46 [PATCH] ip_nat_sip: fix compiler warning Torsten Luettgert
2006-05-28 14:29 ` Patrick McHardy
2006-05-28 15:32 ` Torsten Luettgert [this message]
2006-05-28 15:34 ` Patrick McHardy
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=1148830346.32002.9.camel@scaramouche.combox.de \
--to=t.luettgert@pressestimmen.de \
--cc=kaber@trash.net \
--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.