Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] make linux26-force
Date: Fri, 25 Jun 2010 11:53:28 +0200	[thread overview]
Message-ID: <874ogr4ew7.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <0D753D10438DA54287A00B02708426976372DCA426@AUSP01VMBX24.collaborationhost.net> (H. Hartley Sweeten's message of "Thu, 24 Jun 2010 10:48:09 -0500")

>>>>> "H" == H Hartley Sweeten <hartleys@visionengravers.com> writes:

Hi,

 H> No.  Manually adding a new patch or making a change to one of the
 H> source files will not cause the kernel to be rebuilt.  And, doing a
 H> linux26-menuconfig also will not cause the rebuild (unless something
 H> is changed).

 H> I'm trying to bring up a new board design so I am always making
 H> changes to my kernel board init file, either to enable a new feature
 H> or test something.

I would personally do that kind of work outside buildroot, and build the
kernel manually.

BR is nice for automating stuff once you have the basic config stable,
but I'm not the best option when you do lowlevel kernel work like board
code / device drivers.

But ok, we can readd that option - But where to stop? Some day someone
will want to hack on something else (u-boot/busybox/uClibc/whatever) and
end up in the same situation.
-- 
Bye, Peter Korsgaard

      parent reply	other threads:[~2010-06-25  9:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-23 22:59 [Buildroot] make linux26-force H Hartley Sweeten
2010-06-24  7:23 ` Thomas Petazzoni
2010-06-24 15:48   ` H Hartley Sweeten
2010-06-25  7:24     ` Thomas Petazzoni
2010-06-25  9:53     ` Peter Korsgaard [this message]

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=874ogr4ew7.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --cc=buildroot@busybox.net \
    /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