From: Olof Johansson <olof@lixom.net>
To: Subrata Modak <subrata@linux.vnet.ibm.com>
Cc: netdev <netdev@vger.kernel.org>,
Geoff Levand <geoffrey.levand@am.sony.com>,
Linuxppc-dev <Linuxppc-dev@ozlabs.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next <linux-next@vger.kernel.org>,
sachinp <sachinp@linux.vnet.ibm.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
themann@de.ibm.com, davem@davemloft.net
Subject: INET_LRO as tristate and use from modules (was: Re: [BUILD FAILURE 08/12] Next April 21 : PPC64 randconfig [drivers/net/pasemi_mac_driver.ko])
Date: Tue, 21 Apr 2009 14:33:19 -0500 [thread overview]
Message-ID: <20090421193319.GB20237@lixom.net> (raw)
In-Reply-To: <1240339984.9110.141.camel@subratamodak.linux.ibm.com>
On Wed, Apr 22, 2009 at 12:23:03AM +0530, Subrata Modak wrote:
> Reported this on 9th April earlier:
> http://lkml.org/lkml/2009/4/9/276,
>
> I hope the following Patch will solve this problem as well:
> Geoff Levand <geoffrey.levand@am.sony.com> provided a patch on 17th
> April.
> http://lkml.org/lkml/2009/4/17/313,
No, that's a separate issue.
> MODPOST 338 modules
> ERROR: ".lro_receive_skb" [drivers/net/pasemi_mac_driver.ko] undefined!
> ERROR: ".lro_flush_all" [drivers/net/pasemi_mac_driver.ko] undefined!
> WARNING: modpost: Found 1 section mismatch(es).
> To see full details build your kernel with:
> 'make CONFIG_DEBUG_SECTION_MISMATCH=y'
> make[1]: *** [__modpost] Error 1
> make: *** [modules] Error 2
This seems to be a problem with all tristate-capable drivers that use
LRO (and uses select INET_LRO in their Kconfig): INET_LRO is a tristate
and can thus be a module. Looks like it needs to be a bool instead?
-Olof
next prev parent reply other threads:[~2009-04-21 19:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-21 18:53 [BUILD FAILURE 08/12] Next April 21 : PPC64 randconfig [drivers/net/pasemi_mac_driver.ko] Subrata Modak
2009-04-21 19:33 ` Olof Johansson [this message]
2009-04-22 9:12 ` INET_LRO as tristate and use from modules David Miller
2009-05-08 19:43 ` David Miller
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=20090421193319.GB20237@lixom.net \
--to=olof@lixom.net \
--cc=Linuxppc-dev@ozlabs.org \
--cc=davem@davemloft.net \
--cc=geoffrey.levand@am.sony.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sachinp@linux.vnet.ibm.com \
--cc=sfr@canb.auug.org.au \
--cc=subrata@linux.vnet.ibm.com \
--cc=themann@de.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).