Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ulrich Prinz <uprinz2@netscape.net>
To: buildroot@busybox.net
Subject: [Buildroot] Out of tree kernel sources?
Date: Tue, 09 Aug 2011 22:58:13 +0200	[thread overview]
Message-ID: <4E419F65.8060604@netscape.net> (raw)

Hello to the list!

Im the new guy here, restarting into buildroot again after a few years
pause.

Congrats for the big improvements that where done. Started a simple
trial for a AT91SAM9 device and it worked out of the box. Great!

But I have a question for out of tree source code for the kernel.

I know that you can call the kernels make by passing SRC1DIR= and
SRC2DIR= arguments to prefer these source code directories above the
kernels own ones. This is very comfortable as you can simply copy the to
be modified kernel code there and do whatever you want. So all your
changes collect there and you do not have to search for what you did
yesterday. And you don't have to have a clean kernel copy for diff or to
mess with gis/svn/cvs.

But I cannot find any hint if this is an option in buildroot. Have I
missed it?

Thanks in advance and best regards
Ulrich

             reply	other threads:[~2011-08-09 20:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-09 20:58 Ulrich Prinz [this message]
2011-08-10  1:39 ` [Buildroot] Out of tree kernel sources? Thiago A. Corrêa

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=4E419F65.8060604@netscape.net \
    --to=uprinz2@netscape.net \
    --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