From mboxrd@z Thu Jan  1 00:00:00 1970
From: pebolle@tiscali.nl (Paul Bolle)
Date: Thu, 25 Sep 2014 08:48:37 +0200
Subject: Compile external module against linux source and use
	functionality in linux source
In-Reply-To: <CAKpWUYkOA5_Xc7JWC17ON_stfVr3CzTBgLCdwP-2LS79OhErNg@mail.gmail.com>
References: <CAKpWUYnF7oZiBUMSFPZFNSBDKO78FP=sFKDbavga2Xiut8mS5w@mail.gmail.com>
	<1411627008.6613.4.camel@x220>
	<CAKpWUYkOA5_Xc7JWC17ON_stfVr3CzTBgLCdwP-2LS79OhErNg@mail.gmail.com>
Message-ID: <1411627717.6613.8.camel@x220>
To: kernelnewbies@lists.kernelnewbies.org
List-Id: kernelnewbies.lists.kernelnewbies.org

[Manually corrected top-posting.]

On Thu, 2014-09-25 at 12:11 +0530, Arjun Pandey wrote:
> On Thu, Sep 25, 2014 at 12:06 PM, Paul Bolle <pebolle@tiscali.nl> wrote:
> > I'm guessing you're compiling that module as, well, a module (ie,
> > CONFIG_EXAMPLE=m). What happens when you make it built-in
> > (CONFIG_EXAMPLE=y)?
> >
> No i am just compiling the external module and using this
> functionality in existing linux source code. I am not adding any
> additional modules within the tree which use this function.

So, does the linker error disappear when you build your kernel with your
new module built-in (ie, the new module is part of the kernel image)?
 
> In my case i am trying to use the function directly in udp_rcv
> function of net/ipv4/udp.c


Paul Bolle