Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: David Claffey <david.claffey@rcn.com>
To: buildroot@busybox.net
Subject: [Buildroot] kernel patch not applied
Date: Thu, 10 May 2007 11:34:17 -0400	[thread overview]
Message-ID: <46433B79.50101@rcn.com> (raw)
In-Reply-To: <46432A7D.6050808@rcn.com>

This actually causes an override of the .patched target in
toolchain/kernel-headers/kernel-headers-new.makefile.

Suggestions?

David Claffey wrote:
> I have a custom kernel patch I want applied when building the 2.6 kernel.  I
> created a device under target/devices with a directory kernel-patches and
> BR2_BOARD_PATH set correctly.  However, the patch is never applied apparently
> because all patches are assumed to be minor kernel version patches.
> 
> In the case when DOWNLOAD_LINUX26_VERSION equals LINUX26_VERSION no patches,
> including custom kernel patches, are applied. My current fix below will change
> the directory name if minor kernel patches are applied, but still allow patches
> in $(BR2_BOARD_PATH)/kernel-patches to be applied.
> 
> Could this cause problem elsewhere in the build?
> 
> Index: target/linux26.mk
> ===================================================================
> --- target/linux26.mk     (revision 18593)
> +++ target/linux26.mk     (working copy)
> @@ -74,11 +74,11 @@
>         mv -f $(BUILD_DIR)/linux-$(DOWNLOAD_LINUX26_VERSION) $(LINUX26_DIR)
>  endif
>         touch $@
> +endif # ($(LINUX26_VERSION),$(LINUX_HEADERS_VERSION))
> 
>  $(LINUX26_DIR)/.patched: $(LINUX26_DIR)/.unpacked
>         toolchain/patch-kernel.sh $(LINUX26_DIR) $(LINUX26_PATCH_DIR)
>         touch $@
> -endif # ($(LINUX26_VERSION),$(LINUX_HEADERS_VERSION))
> 
>  $(LINUX26_DIR)/.configured:  $(LINUX26_DIR)/.patched  $(LINUX26_KCONFIG)
>         cp -dpf $(LINUX26_KCONFIG) $(LINUX26_DIR)/.config
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot
> 

  reply	other threads:[~2007-05-10 15:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-10 14:21 [Buildroot] kernel patch not applied David Claffey
2007-05-10 15:34 ` David Claffey [this message]
2007-05-11 14:31   ` Hans-Christian Egtvedt
2007-05-11 15:40     ` Bernhard Fischer
2007-05-11 16:29       ` David Claffey
2007-05-12 10:31         ` Bernhard Fischer
2007-05-29 20:52           ` David Claffey
2007-05-14  5:21       ` Hans-Christian Egtvedt
2007-05-14  7:11         ` Bernhard Fischer
2007-05-14 12:41           ` [Buildroot] Matchbox Support Christopher Reder
2007-05-15  8:46             ` Assen Stoyanov
2007-05-15 10:55               ` Peter Korsgaard
2007-05-14 15:25           ` [Buildroot] kernel patch not applied Hans-Christian Egtvedt
2007-05-14 15:34             ` Bernhard Fischer
2007-05-15  7:47               ` Hans-Christian Egtvedt
2007-05-15  8:53                 ` Bernhard Fischer
2007-05-15 10:35                   ` [Buildroot] Whats happened to Eric? Ulf Samuelsson
2007-05-15 19:04                     ` Erik Andersen
2008-11-04 18:19           ` [Buildroot] kernel patch not applied Julien Boibessot
2008-11-04 19:54             ` Bernhard Reutner-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=46433B79.50101@rcn.com \
    --to=david.claffey@rcn.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