From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Redundant kernel patches in the snapshot from20070718
Date: Tue, 31 Jul 2007 10:38:58 +0200 [thread overview]
Message-ID: <20070731083858.GA3797@aon.at> (raw)
In-Reply-To: <1185839954.30603.36.camel@elrond.sweden.atmel.com>
On Tue, Jul 31, 2007 at 01:59:14AM +0200, Ulf Samuelsson wrote:
Can we settle on the following procedure:
You provide a full patch that does the final migration to unpack and
patch a kernel for each project, install it's headers into the project
specific dir (from within target/linux/Makefile.in, if you prefer).
I'd like to review (and eventually discuss) this patch before it is
finally committed.
Whether you rm toolchain/kernel-headers or not (and how you deal with
kernel-headers-old vs. kernel-header-new) is up to you. I just want to
do this migration in one (tested) step.
Most of the needed steps do already exist, it's merely a matter of
unpacking the kernel in the project specific dir and decide how to
handle patches, i.e. whether to only apply exact patches or try to apply
them if they _could_ do the right thing.
Ok?
next prev parent reply other threads:[~2007-07-31 8:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-26 14:23 [Buildroot] Redundant kernel patches in the snapshot from 20070718 Hans-Christian Egtvedt
2007-07-26 16:52 ` Ulf Samuelsson
2007-07-27 11:30 ` Bernhard Fischer
2007-07-30 15:51 ` [Buildroot] Redundant kernel patches in the snapshot from20070718 Ulf Samuelsson
2007-07-30 19:27 ` Bernhard Fischer
2007-07-30 20:02 ` Bernhard Fischer
2007-07-30 23:59 ` Ulf Samuelsson
2007-07-31 8:38 ` Bernhard Fischer [this message]
2007-08-01 7:03 ` [Buildroot] Redundant kernel patches in the snapshotfrom20070718 Ulf Samuelsson
2007-07-30 23:53 ` [Buildroot] Redundant kernel patches in the snapshot from20070718 Ulf Samuelsson
2007-07-27 10:59 ` [Buildroot] Redundant kernel patches in the snapshot from 20070718 Bernhard Fischer
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=20070731083858.GA3797@aon.at \
--to=rep.dot.nop@gmail.com \
--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