From: Hans-Christian Egtvedt <hcegtvedt@norway.atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] Redundant kernel patches in the snapshot from 20070718
Date: Thu, 26 Jul 2007 16:23:18 +0200 [thread overview]
Message-ID: <1185459798.1044.43.camel@localhost.localdomain> (raw)
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?
--
Mvh
Hans-Christian Egtvedt
next reply other threads:[~2007-07-26 14:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-26 14:23 Hans-Christian Egtvedt [this message]
2007-07-26 16:52 ` [Buildroot] Redundant kernel patches in the snapshot from 20070718 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 ` [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=1185459798.1044.43.camel@localhost.localdomain \
--to=hcegtvedt@norway.atmel.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