From: Harald Welte <laforge@netfilter.org>
To: Benoit Boissinot <benoit.boissinot@ens-lyon.org>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [patch 2.6.15-mm4] fix warning in ip{,6}t_policy.c
Date: Sat, 14 Jan 2006 21:38:19 +0100 [thread overview]
Message-ID: <20060114203818.GE6740@sunbeam.de.gnumonks.org> (raw)
In-Reply-To: <20060114180917.GA26443@ens-lyon.fr>
[-- Attachment #1: Type: text/plain, Size: 1116 bytes --]
On Sat, Jan 14, 2006 at 07:09:17PM +0100, Benoit Boissinot wrote:
> Hi,
>
> the following warnings appeared in -mm4
> net/ipv4/netfilter/ipt_policy.c:154: warning: initialization from incompatible pointer type
> net/ipv4/netfilter/ipt_policy.c:155: warning: initialization from incompatible pointer type
> net/ipv6/netfilter/ip6t_policy.c:160: warning: initialization from incompatible pointer type
oops, sorry. my mistake when merging patricks' ipt_policy code with
x_tables.
> It looks like they were missed in the x_tables conversion.
yes, since they were developed separately and only later merged.
> Signed-off-by: Benoit Boissinot <benoit.boissinot@ens-lyon.org>
I'll push this without any modifications via DaveM.
--
- Harald Welte <laforge@netfilter.org> http://netfilter.org/
============================================================================
"Fragmentation is like classful addressing -- an interesting early
architectural error that shows how much experimentation was going
on while IP was being designed." -- Paul Vixie
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2006-01-14 20:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-14 18:09 Benoit Boissinot
2006-01-14 20:38 ` Harald Welte [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=20060114203818.GE6740@sunbeam.de.gnumonks.org \
--to=laforge@netfilter.org \
--cc=akpm@osdl.org \
--cc=benoit.boissinot@ens-lyon.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®