All of lore.kernel.org
 help / color / mirror / Atom feed
From: ydroneaud@opteya.com (Yann Droneaud)
To: kernelnewbies@lists.kernelnewbies.org
Subject: question about building a module
Date: Sat, 08 Dec 2012 09:03:16 +0100	[thread overview]
Message-ID: <1354953796.27902.9.camel@test.quest-ce.net> (raw)
In-Reply-To: <CAGXs5wW1kzfkVpVgOfyQWfeRwkb0g6dME9e=njOXtUENy0iNNA@mail.gmail.com>

Le vendredi 07 d?cembre 2012 ? 20:44 +0200, Kevin Wilson a ?crit :
> Hi,
> 
> 
> I am adding some code of my own **only** under 
> net/bluetooth in some file there.
> 
> 
> There is only exactly one module which is changed by my addition,
> This is net/bluetooth/bluetooth.ko
> 
> 
> Now, when I run 'make -j2 modules' it takes quite a time, even If I 
> did one change in one line in a file under net/bluetooth.
> 
> 
> I assume that it has to do with stage 2 of the build, which says
> something about 
> ...
>   Building modules, stage 2.
>   MODPOST 855 modules
> ...
> see below full log.
> 
> 
> Now my question is this:
> Is there a way to make things more efficent when building a module, on
> the 
> assumption that I do not change anything anywhere
> except /net/bluetooth (in this case)?
> 
> 
> somehow telling the MODPOST  that only one module is changes ? 
> 
> 
> I remember I once saw (not sure) a suggestion to build only a
> specified moule like: 
> make net/bluetooth
> But in this case the result is the same.
> 

cd net/bluetooth
make -C $PWD/../../ M=$PWD modules

(But if you change a configuration parameter in .config,
you will need to do a full build)

Regards.

-- 
Yann Droneaud
OPTEYA

  reply	other threads:[~2012-12-08  8:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-07 18:44 question about building a module Kevin Wilson
2012-12-08  8:03 ` Yann Droneaud [this message]
2012-12-08  9:02   ` devendra.aaru
2012-12-08 18:16     ` Yann Droneaud

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=1354953796.27902.9.camel@test.quest-ce.net \
    --to=ydroneaud@opteya.com \
    --cc=kernelnewbies@lists.kernelnewbies.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 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.