From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] board: mini2440: Add custom patches and configs for 2.6.38 kernel series.
Date: Tue, 17 May 2011 10:53:38 +0200 [thread overview]
Message-ID: <20110517105338.0fe0db78@surf> (raw)
In-Reply-To: <BANLkTi=nd4=RF2mGFMFGZhRp25B+UOmDmw@mail.gmail.com>
On Tue, 17 May 2011 10:48:56 +0200
Belisko Marek <marek.belisko@gmail.com> wrote:
> >>> Patching kernel
> for p in board/friendlyarm/mini2440/ ; do \
> if echo $p | grep -q -E "^ftp://|^http://" ; then \
> toolchain/patch-kernel.sh
> /home/open-nandra/projects/buildroot/output/build/linux-2.6.38.6
> /home/open-nandra/projects/buildroot/dl `basename $p` ; \
> elif test -d $p ; then \
> toolchain/patch-kernel.sh
> /home/open-nandra/projects/buildroot/output/build/linux-2.6.38.6 $p
> linux-\*.patch ; \
> else \
> toolchain/patch-kernel.sh
> /home/open-nandra/projects/buildroot/output/build/linux-2.6.38.6
> `dirname $p` `basename $p` ; \
> fi \
> done
> >>> Configuring kernel
>
> Any idea why???
They must be named linux-*.patch. See
toolchain/patch-kernel.sh /home/open-nandra/projects/buildroot/output/build/linux-2.6.38.6 $p linux-\*.patch ; \
in the "test -d $p" case.
In your board directory, you can store patches for Linux, patches for
U-Boot, patches for Barebox or whatever, so it makes sense to keep a
linux- prefix, in my opinion.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-05-17 8:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 6:55 [Buildroot] [PATCH] board: mini2440: Add custom patches and configs for 2.6.38 kernel series Marek Belisko
2011-05-17 7:40 ` Thomas Petazzoni
2011-05-17 8:48 ` Belisko Marek
2011-05-17 8:53 ` Thomas Petazzoni [this message]
2011-05-17 9:21 ` Vasily Khoruzhick
2011-05-17 9:31 ` Belisko Marek
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=20110517105338.0fe0db78@surf \
--to=thomas.petazzoni@free-electrons.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