All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Ziegler <patrick.ziegler@fh-kl.de>
To: buildroot@busybox.net
Subject: [Buildroot] kernel header patches
Date: Mon, 09 Aug 2010 09:16:46 +0200	[thread overview]
Message-ID: <4C5FAB5E.1090901@fh-kl.de> (raw)
In-Reply-To: <4C5BF511.8070704@gmx.net>



Ossy schrieb:
> Am 02.08.2010 10:01, schrieb Patrick Ziegler:
>>
>> Is there an official way to apply patches to the kernel headers and
>> kernel sources depending on the board ?
>>
> For my Board I need to apply some minor patches to the kernel. My
> configuration looks like this:
>
> Location of patches in project tree:
> target/device/sheevaplug/SeagateDockStar/kernel-patches/
> -> linux-2.6.34-0001-ABC.patch
> -> linux-2.6.34-0002-XYZ.patch
> -> DONOTUSENOW-linux-2.6.34-0002-XYZTesting.patch
>
> .config includes:
> BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
> BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="target/device/sheevaplug/SeagateDockStar/SeagateDockStar-linux-2.6.34.1.config"
>
> BR2_LINUX_KERNEL_PATCH="target/device/sheevaplug/SeagateDockStar/kernel-patches/"
>
>
> The patches were correctly applied during kernel compilation via
> buildroot.

Thanks, but unfortunately this works only for the kernel compilation not
for the kernel headers.

-- 

Dipl.-Inf. (FH) Patrick Ziegler

University Of Applied Sciences
Kaiserslautern

Amerikastrasse 1
D-66482 Zweibruecken
Germany

Phone:	+49 6332 914 526
Mail:	patrick.ziegler at fh-kl.de

http://www.fh-kl.de
http://www.fh-kl.de/fachbereiche/imst/iuk-knowhow.html

      reply	other threads:[~2010-08-09  7:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-02  8:01 [Buildroot] kernel header patches Patrick Ziegler
2010-08-06 11:42 ` Ossy
2010-08-09  7:16   ` Patrick Ziegler [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=4C5FAB5E.1090901@fh-kl.de \
    --to=patrick.ziegler@fh-kl.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.