From: Christoph Hellwig <hch@infradead.org>
To: Subbu Seetharaman <subbus@serverengines.com>
Cc: Sam Ravnborg <sam@ravnborg.org>,
jeff@garzik.org, netdev@vger.kernel.org,
sathyap@serverengines.com
Subject: Re: [PATCH 3/12] benet: net_object i/f functions, Makefile
Date: Thu, 19 Jun 2008 05:11:35 -0400 [thread overview]
Message-ID: <20080619091135.GA11101@infradead.org> (raw)
In-Reply-To: <20080619062701.46a98ab1@mailhost.serverengines.com>
On Wed, Jun 18, 2008 at 11:27:01PM -0700, Subbu Seetharaman wrote:
> We could not get KBUILD_EXTRA_SYMBOLS to work.
> This is what we did :
>
> beclib's Module.symvers has entries like this :
>
> 0x00000000 be_eq_destroy /home/subbu/kod39-sperla/drivers/message/beclib/beclib EXPORT_SYMBOL
>
> benet uses exports from beclib and we have the following line in benet's Makefile:
> KBUILD_EXTRA_SYMBOLS = $(src)/../../message/beclib/Module.symvers
>
> When we build benet we still get warnings like this
> for symbols defined and exported from beclib :
> WARNING: "be_eq_destroy" [/home/subbu/kod39-sperla/drivers/net/benet/benet.ko] undefined!
>
The righ answer is of course to kill all this beclib junk and write
a proper linux driver. We're made it pretty clear a few times in the
past that these abstraction layers don't go in.
next prev parent reply other threads:[~2008-06-19 9:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-19 6:27 [PATCH 3/12] benet: net_object i/f functions, Makefile Subbu Seetharaman
2008-06-19 9:11 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-06-19 9:59 Subbu Seetharaman
2008-06-19 10:01 ` Christoph Hellwig
2008-06-18 16:20 Subbu Seetharaman
2008-06-18 18:41 ` Sam Ravnborg
2008-06-12 10:40 Subbu Seetharaman
2008-06-17 19:26 ` Sam Ravnborg
2008-06-19 10:13 ` Christoph Hellwig
2008-06-19 10:16 ` Christoph Hellwig
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=20080619091135.GA11101@infradead.org \
--to=hch@infradead.org \
--cc=jeff@garzik.org \
--cc=netdev@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=sathyap@serverengines.com \
--cc=subbus@serverengines.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).