mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dragoslav Zaric <dragoslav.zaric.kd@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Test some kernel feature without recompile
Date: Mon, 23 Mar 2009 09:52:19 +0100	[thread overview]
Message-ID: <2d05c4580903230152q24c1625bu3b13a8a3c0fd3ce0@mail.gmail.com> (raw)
In-Reply-To: <2d05c4580903230151n20c8fc7kb47a5e2bb2480591@mail.gmail.com>

Well it looks like I didn't read about "make" command a lot :)
This is what I found :

--------------------------------------------------------------------------------------------------------------------------------------------------------
| Once a suitable Makefile exists, each time you change some source
files, this simple shell command:
|
|    make
|
| suffices to perform all necessary recompilations. The make program
uses the makefile data base and
| the last-modification times of the files to decide which of the
files need to be updated. For each of those
| files, it issues the commands recorded in the data base.
--------------------------------------------------------------------------------------------------------------------------------------------------------

So this is what I would (will) do if I want to debug, change or add
some kernel feature and don't want to wait a
lot of time every time :) :

Build version of kernel that has minimum modules (and other stuff) to
run your machine (unchecked things in
.config file will decrease time) and when work on some feature, then
add just stuff you wanna debug or
change and then run

make

thanks,

dragoslav

  reply	other threads:[~2009-03-23  8:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-22 10:43 Dragoslav Zaric
2009-03-22 11:04 ` Jaswinder Singh Rajput
2009-03-22 11:42 ` Willy Tarreau
2009-03-22 20:29 ` Jesper Juhl
2009-03-23  8:51   ` Dragoslav Zaric
2009-03-23  8:52     ` Dragoslav Zaric [this message]
2009-03-23  3:21 ` Bryan Donlan

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=2d05c4580903230152q24c1625bu3b13a8a3c0fd3ce0@mail.gmail.com \
    --to=dragoslav.zaric.kd@gmail.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

all inboxes | Powered by JetHome®