From: Harald Welte <laforge@netfilter.org>
To: David Miller <davem@davemloft.net>
Cc: gorcunov@gmail.com, randy.dunlap@oracle.com, pablo@netfilter.org,
sfr@canb.auug.org.au, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
kaber@trash.net, netfilter-devel@vger.kernel.org
Subject: Re: linux-next: Tree for March 27 (netfilter build error)
Date: Sun, 29 Mar 2009 13:48:33 +0200 [thread overview]
Message-ID: <20090329114833.GM15306@prithivi.gnumonks.org> (raw)
In-Reply-To: <20090328.234739.26481917.davem@davemloft.net>
[-- Attachment #1: Type: text/plain, Size: 1710 bytes --]
Hi Dave,
On Sat, Mar 28, 2009 at 11:47:39PM -0700, David Miller wrote:
> From: Cyrill Gorcunov <gorcunov@gmail.com>
> Date: Sun, 29 Mar 2009 10:47:04 +0400
>
> > [Randy Dunlap - Sat, Mar 28, 2009 at 09:26:42PM -0700]
> > ...
> > | works_for_me. Thanks.
> > | but missing S-O-B.
> > |
> > | Acked-by: Randy Dunlap <randy.dunlap@oracle.com>
> > ...
> >
> > Thanks for testing Randy. So if nobody will complain
> > here is a solid version of the patch. Though I would like
> > if Pablo or Patrick confirm its correctness. Thanks!
>
> I'll apply this once Patrick or Pablo have a look at it.
I'm neither of them but I strongly believe the patch is correct.
The only question that Patrick raised during the discussion of this patch some
days ago is whether the __ipv6_addr_type() call would cause a runtime
dependency to thei ipv6 module. This would be bad since loading the
xt_cluster.ko module should not pull in the IPv6 protocol module.
I have just verified that __ipv6_addr_type is provided by
net/ipv6/addrconf_core.c, which specifically states it contains functions
"needed by static components when full IPv6 support is not configured or
static". This is confirmed by the makefile, which addes addrconf_core.o to
obj-y.
So from my point of view, I cannot see any problems.
Regards.
--
- 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: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2009-03-29 18:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-27 12:19 linux-next: Tree for March 27 Stephen Rothwell
2009-03-27 16:48 ` linux-next: Tree for March 27 (netfilter build error) Randy Dunlap
2009-03-27 23:01 ` David Miller
2009-03-28 10:28 ` Cyrill Gorcunov
2009-03-29 4:26 ` Randy Dunlap
2009-03-29 6:47 ` Cyrill Gorcunov
2009-03-29 6:47 ` David Miller
2009-03-29 11:48 ` Harald Welte [this message]
2009-03-29 11:59 ` Pablo Neira Ayuso
2009-03-29 12:27 ` Cyrill Gorcunov
2009-03-29 20:46 ` David Miller
2009-03-30 12:00 ` Patrick McHardy
2009-03-27 17:42 ` linux-next: Tree for March 27 (longhaul " Bartlomiej Zolnierkiewicz
2009-03-27 20:44 ` Len Brown
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=20090329114833.GM15306@prithivi.gnumonks.org \
--to=laforge@netfilter.org \
--cc=davem@davemloft.net \
--cc=gorcunov@gmail.com \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=randy.dunlap@oracle.com \
--cc=sfr@canb.auug.org.au \
/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®