public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Américo Wang" <xiyou.wangcong@gmail.com>
To: Alex Bennee <kernel-hacker@bennee.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Problems using EXPORT_SYMBOL with lib/flex_array
Date: Thu, 2 Dec 2010 00:19:27 +0800	[thread overview]
Message-ID: <20101201161927.GC9337@hack> (raw)
In-Reply-To: <AANLkTim=srU8kv-DwL4jgwRS-yH8WN34PgCqsijZvYeV@mail.gmail.com>

On Wed, Dec 01, 2010 at 01:20:30PM +0000, Alex Bennee wrote:
>On 1 December 2010 12:05, Alex Bennee <kernel-hacker@bennee.com> wrote:
>> Hi,
>>
>> I want to be able to use the flex_array functions in my module so I
>> wanted to EXPORT_SYMBOL the API.
>> <snip>
>> Am I being a
>> little dim or is there some other magic foo that needs doing to add an
>> export to a library function?
>
>It turns out for library code there is. If the .o is only included in
>the lib-y section then it will never get scanned for exported kernel
>symbols. Tweaking the lib/Makefile so obj-y included flex_array.o did
>the trick.
>
>I'm unsure if this behaviour is what is wanted?
>

Yes, but not sure about flex_array.o.
Which functions in flex_array.c do you need in your module anyway?

-- 
Live like a child, think like the god.
 

  reply	other threads:[~2010-12-01 16:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-01 12:05 Problems using EXPORT_SYMBOL with lib/flex_array Alex Bennee
2010-12-01 13:20 ` Alex Bennee
2010-12-01 16:19   ` Américo Wang [this message]
2010-12-01 17:33     ` Alex Bennee
2010-12-02  1:16 ` [patch] flex_array: export symbols to modules David Rientjes
2010-12-02  6:30   ` Paul Mundt
2010-12-02  6:57     ` Américo Wang
2010-12-02  6:56       ` Paul Mundt
2010-12-02 23:44     ` [patch v2] " David Rientjes

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=20101201161927.GC9337@hack \
    --to=xiyou.wangcong@gmail.com \
    --cc=kernel-hacker@bennee.com \
    --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