From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Avoiding patching kernel with uneeded things
Date: Thu, 2 Aug 2007 10:50:52 +0200 [thread overview]
Message-ID: <20070802085051.GK11697@aon.at> (raw)
In-Reply-To: <1185998620.10521.18.camel@elrond.sweden.atmel.com>
On Wed, Aug 01, 2007 at 10:03:40PM +0200, Ulf Samuelsson wrote:
>Today we first patch the headers with
> "linux-$(LINUX_HEADERS_VERSION)-\*.patch{,.gz,.bz2}"
>and then with the openswan patches, if openswan is selected.
>
>
>If we added a line to patch an architecture specific patch,
>I.E:
> "linux-$(LINUX_HEADERS_VERSION)-\*.patch{,.gz,.bz2}"
> "$(ARCH)-linux-$(LINUX_HEADERS_VERSION)-\*.patch{,.gz,.bz2}"
> openswan
>then the AVR32 patches would only be applied, if the BR2_avr32 is set.
>
>
>The AVR32 patches would have to be renamed of course.
>
>Any disagreement?
Just put your atmel patches into target/ATMEL/kernel-patches so they
don't interfere with other arches.
prev parent reply other threads:[~2007-08-02 8:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 20:03 [Buildroot] Avoiding patching kernel with uneeded things Ulf Samuelsson
2007-08-02 8:50 ` 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=20070802085051.GK11697@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