All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulf@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] linux-2.6.21.5-003-atmel.1-avr32-updates.patchfailes
Date: Wed, 1 Aug 2007 08:20:01 +0200	[thread overview]
Message-ID: <015801c7d404$0f9291d0$dcc4af0a@atmel.com> (raw)
In-Reply-To: 0707312209460.11633@somehost

>> Conflicts between linux-2.6.21.5-002-lzma-vmlinuz.01.patch and
>> linux-2.6.21.5-003-atmel.1-avr32-updates.patch?
> 
> Questions:
> 
> Is it really necessary to apply these patches? Even though .config shows?
> 
> # BR2_PACKAGE_LZMA_TARGET is not set
> # BR2_PACKAGE_LZMA_HOST is not set
> # BR2_TARGET_ROOTFS_EXT2_LZMA is not set
> # BR2_avr32 is not set
> # BR2_TOOLCHAIN_ATMEL_AVR32 is not set
> 
> Wouldn't it be a good idea for each successfully applied patch to have a
> target and a prequisite?
> 
> <patch name>: <patch name>.done
> 
> so that, if a patch fails and is fixed on the spot, remake skipps the
> already applied patches?
> 

We are currently discussing the mess with separate patch strategies
for the kernel headers and the linux build.
I proposed that both the kernel-headers and the linux should use the same patch directories.
This is only the case, if the kernel-headers and the linux version are the same today.

A long term approach could be to keep the kernel-headers for pre 2.6.19 kernels only
and build the headers in the target/linux directory, with patches
divided into groups of patches which are or are not applied depending on 
menu configurations.

Typically you would have 
"core" patches              - always applied
"architecture" patches   - always applied if an architecture is selected
"board" patches            -  conditionally applied through a choice.

Best Regards
Ulf Samuelsson

  reply	other threads:[~2007-08-01  6:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-31 19:51 [Buildroot] linux-2.6.21.5-003-atmel.1-avr32-updates.patch failes Cristian Ionescu-Idbohrn
2007-07-31 19:56 ` Cristian Ionescu-Idbohrn
2007-07-31 20:19   ` Cristian Ionescu-Idbohrn
2007-08-01  6:20     ` Ulf Samuelsson [this message]
2007-08-01 10:36     ` Bernhard Fischer
2007-08-01 11:50       ` Ulf Samuelsson
2007-07-31 22:52 ` Ulf Samuelsson

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='015801c7d404$0f9291d0$dcc4af0a@atmel.com' \
    --to=ulf@atmel.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.