All of lore.kernel.org
 help / color / mirror / Atom feed
From: Will Wagner <will_wagner@carallon.com>
To: buildroot@busybox.net
Subject: [Buildroot] Problem patching linux
Date: Fri, 14 Mar 2008 12:55:14 +0000	[thread overview]
Message-ID: <47DA75B2.50004@carallon.com> (raw)

Hi All,

I have a custom board in target/device/my_board. Inside that folder I 
have a kernel_patches folder and I have changed the config so that it 
should apply my patches.

It all works when applying the patches for the kernel headers, but it 
fails to patch the actual kernel. This is because of the different ways 
the patch-kernel.sh script is called.

In kernel-headers-new.makefile it is:
	toolchain/patch-kernel.sh $(LINUX_HEADERS_UNPACK_DIR) 
$(KERNEL_HEADERS_PATCH_DIR) \
		\*.patch{,.gz,.bz2}

But in the linux Makefile.in it is:
	toolchain/patch-kernel.sh $(LINUX26_DIR) $(KERNEL_HEADERS_PATCH_DIR) \
		linux-$(LINUX26_VERSION)-\*.patch{,.gz,.bz2}

The regex is much tougher when actually patching the kernel. The problem 
I have it that my patch files are all in this format:

012-linux-2.6.22.19-some_patch

I need the numbers at the beginning to ensure they get patched in the 
right order.

How should I fix this? How should my patch files be named? Is this just 
a bug in the patching of the kernel?

Thanks,

Will.
-- 
------------------------------------------------------------------------
Will Wagner                                     will_wagner at carallon.com
Senior Project Engineer                  Office Tel: +44 (0)20 7371 2032
Carallon Ltd, Studio G20, Shepherds Building, Rockley Rd, London W14 0DA
------------------------------------------------------------------------

             reply	other threads:[~2008-03-14 12:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-14 12:55 Will Wagner [this message]
2008-03-14 17:12 ` [Buildroot] Problem patching linux John Voltz

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=47DA75B2.50004@carallon.com \
    --to=will_wagner@carallon.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 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.