From: Patrick McHardy <kaber@trash.net>
To: Darren Jenkins <darrenrjenkins@gmail.com>
Cc: kernel Janitors <kernel-janitors@lists.osdl.org>,
"Randy.Dunlap" <rdunlap@xenotime.net>,
netfilter-devel@lists.netfilter.org
Subject: [KJ] Re: fix kbuild warning in iptable_nat.o
Date: Wed, 05 Apr 2006 22:00:04 +0000 [thread overview]
Message-ID: <44343DE4.70500@trash.net> (raw)
In-Reply-To: <1143719875.8469.14.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 877 bytes --]
Darren Jenkins\ wrote:
> G'day list
>
> There are a couple of Kbuild warnings in net/ipv4/netfilter/ that would
> be nice to get rid of.
>
> WARNING: net/ipv4/netfilter/ip_conntrack.o - Section mismatch: reference
> to .init.text:ip_conntrack_init from .text between 'init_or_cleanup' (at
> offset 0x7ea) and '__hash_conntrack'
> WARNING: net/ipv4/netfilter/iptable_nat.o - Section mismatch: reference
> to .init.text:ip_nat_rule_init from .text between 'init_or_cleanup' (at
> offset 0x455) and 'nat_decode_session'
>
> I have a patch for the 'iptable_nat.o' warning below, and I was just
> wanting to check in and see if any of you netfilter guys had a problem
> with this patch, or with me doing a similar patch for the
> 'ip_canntrack.o' warning.
>
>
> Any input would be welcome, thanks in advance :).
I have a patch queued that just splits the init/cleanup parts.
[-- Attachment #2: Type: text/plain, Size: 168 bytes --]
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors
WARNING: multiple messages have this Message-ID (diff)
From: Patrick McHardy <kaber@trash.net>
To: "Darren Jenkins" <darrenrjenkins@gmail.com>
Cc: kernel Janitors <kernel-janitors@lists.osdl.org>,
"Randy.Dunlap" <rdunlap@xenotime.net>,
netfilter-devel@lists.netfilter.org
Subject: Re: fix kbuild warning in iptable_nat.o
Date: Thu, 06 Apr 2006 00:00:04 +0200 [thread overview]
Message-ID: <44343DE4.70500@trash.net> (raw)
In-Reply-To: <1143719875.8469.14.camel@localhost.localdomain>
Darren Jenkins\ wrote:
> G'day list
>
> There are a couple of Kbuild warnings in net/ipv4/netfilter/ that would
> be nice to get rid of.
>
> WARNING: net/ipv4/netfilter/ip_conntrack.o - Section mismatch: reference
> to .init.text:ip_conntrack_init from .text between 'init_or_cleanup' (at
> offset 0x7ea) and '__hash_conntrack'
> WARNING: net/ipv4/netfilter/iptable_nat.o - Section mismatch: reference
> to .init.text:ip_nat_rule_init from .text between 'init_or_cleanup' (at
> offset 0x455) and 'nat_decode_session'
>
> I have a patch for the 'iptable_nat.o' warning below, and I was just
> wanting to check in and see if any of you netfilter guys had a problem
> with this patch, or with me doing a similar patch for the
> 'ip_canntrack.o' warning.
>
>
> Any input would be welcome, thanks in advance :).
I have a patch queued that just splits the init/cleanup parts.
next prev parent reply other threads:[~2006-04-05 22:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-30 11:57 [KJ] fix kbuild warning in iptable_nat.o Darren Jenkins\
2006-03-30 11:57 ` Darren Jenkins\
2006-04-05 22:00 ` Patrick McHardy [this message]
2006-04-05 22:00 ` 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=44343DE4.70500@trash.net \
--to=kaber@trash.net \
--cc=darrenrjenkins@gmail.com \
--cc=kernel-janitors@lists.osdl.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=rdunlap@xenotime.net \
/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.