From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] New kernel source mode [Proposal]
Date: Sat, 19 Jan 2013 17:16:44 +0100 [thread overview]
Message-ID: <50FAC6EC.8030807@mind.be> (raw)
In-Reply-To: <EE5E77B503DE9A478B63A89AAD2585EDB66A2F@vpane.excalyptech.com>
On 15/01/13 02:12, Przemyslaw Wrzos wrote:
> Hi,
>
> I?d like to get some feedback on a feature I?d like to contribute to the
> buildroot project. I?m not quite sure what the process is so I thought
> I?d start on the mailing list.
>
> PROPOSAL: Allow a directory (containing the source tree) to be used as
> the source for the kernel build. The source isn?t copied to the output
> directory but instead the kernel?s outputmakfile wrapper facility is used.
>
A patch with similar functionality was posted in August by Sonic Zhang:
http://patchwork.ozlabs.org/patch/177618/
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
prev parent reply other threads:[~2013-01-19 16:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 1:12 [Buildroot] New kernel source mode [Proposal] Przemyslaw Wrzos
2013-01-15 7:51 ` Stephan Hoffmann
2013-01-17 6:25 ` Przemyslaw Wrzos
2013-01-17 6:27 ` Przemyslaw Wrzos
2013-01-18 1:10 ` Przemyslaw Wrzos
2013-01-18 8:14 ` Stephan Hoffmann
2013-01-21 0:23 ` Przemyslaw Wrzos
2013-01-15 7:55 ` Thomas Petazzoni
2013-01-15 8:18 ` Jeremy Rosen
2013-01-15 8:22 ` Thomas Petazzoni
2013-01-15 9:13 ` Jeremy Rosen
2013-01-15 9:24 ` Thomas Petazzoni
2013-01-15 9:27 ` Jeremy Rosen
2013-01-19 16:13 ` Arnout Vandecappelle
2013-01-17 6:59 ` Przemyslaw Wrzos
2013-01-15 18:23 ` Steve Calfee
2013-01-15 20:40 ` Peter Korsgaard
2013-01-19 16:16 ` Arnout Vandecappelle [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=50FAC6EC.8030807@mind.be \
--to=arnout@mind.be \
--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