All of lore.kernel.org
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: What is the fastest way to build and boot a kernel
Date: Tue, 18 Apr 2017 18:07:11 +0200	[thread overview]
Message-ID: <20170418160711.GA29610@kroah.com> (raw)
In-Reply-To: <CABGNeczftD4Sn+g=uQM7NpxH9pC3i1i110ER4rbu-awcZRkXgQ@mail.gmail.com>

On Tue, Apr 18, 2017 at 08:59:36AM -0700, Code Soldier1 wrote:
> Hi,
> 
> Can someone suggest what is the fastest way to build a minimal kernel
> and boot. For example if I am working on TCP and would like to make a
> small change and reboot, what is the fastest way, I rather not build
> the whole kernel.

Why would you need to rebuild the whole kernel?  What did you change
that required everything to be rebuilt?

And a working kernel can normally be built, from scratch, in just a few
minutes.  You do know about 'make localmodconfig' right?

thanks,

greg k-h

  reply	other threads:[~2017-04-18 16:07 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-18 15:59 What is the fastest way to build and boot a kernel Code Soldier1
2017-04-18 16:07 ` Greg KH [this message]
2017-04-18 17:38   ` Code Soldier1
2017-04-18 17:42     ` Peter Senna Tschudin
2017-04-18 17:44     ` Greg KH
2017-04-18 18:04       ` Code Soldier1
2017-04-18 18:15         ` Guru Das S
2017-04-25 13:15           ` Manoj
2017-04-19 10:32 ` Tobin C. Harding
2017-04-19 10:49   ` valdis.kletnieks at vt.edu
2017-04-19 12:43     ` Aruna Hewapathirane
2017-04-19 18:26   ` Code Soldier1
2017-04-20  8:21     ` Sébastien Masson
2017-04-20 16:20       ` Code Soldier1
2017-04-20 16:31         ` Alexander Kapshuk
2017-04-20 16:54           ` Joe Smith
2017-04-20 17:50             ` Bjørn Mork
2017-04-20 19:27               ` Joe Smith
2017-04-21  8:43                 ` Bjørn Mork
2017-04-19 11:24 ` Aruna Hewapathirane
2017-04-19 17:10 ` Stephen Brennan

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=20170418160711.GA29610@kroah.com \
    --to=greg@kroah.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.