From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Redundant kernel patches in the snapshot from 20070718
Date: Fri, 27 Jul 2007 12:59:21 +0200 [thread overview]
Message-ID: <20070727105921.GE22789@aon.at> (raw)
In-Reply-To: <1185459798.1044.43.camel@localhost.localdomain>
On Thu, Jul 26, 2007 at 04:23:18PM +0200, Hans-Christian Egtvedt wrote:
>Hello,
>
>I am a bit confused to where I should put the kernel patch, there seems
>to be two places expecting the same file.
>
>toolchain/kernel-headers/kernel-headers-new.makefile expects them to be
>in toolchain/kernel-headers.
>
>target/linux/Makefile.in expects them to be in
>$(BR2_BOARD_PATH)/kernel-patches.
>
>AFAICT this is redundant, what is the need to put the same patches in a
>board specific folder? Should the target/linux/Makefile.in first do the
>patches in toolchain/kernel-headers and then
>$(BR2_BOARD_PATH)/kernel-patches if it exists?
yes.
as a general rant, such board-specific patches tend do break other
configurations more often than not (in my experience).
I added it for cases like a special device-driver which is not worth
downloading when building for a different arch.
HTH,
prev parent reply other threads:[~2007-07-27 10:59 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
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 ` Bernhard Fischer [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=20070727105921.GE22789@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