All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cristian Ionescu-Idbohrn <cristian.ionescu-idbohrn@axis.com>
To: buildroot@busybox.net
Subject: [Buildroot] linux-2.6.21.5-003-atmel.1-avr32-updates.patch failes
Date: Tue, 31 Jul 2007 21:56:09 +0200 (CEST)	[thread overview]
Message-ID: <0707312154000.11633@somehost> (raw)
In-Reply-To: <0707312150570.11633@somehost>

Preceeded by this:

Applying linux-2.6.21.5-002-lzma-vmlinuz.01.patch using plaintext:
patching file arch/i386/boot/compressed/Makefile
patching file scripts/gen_lzma_initramfs_list.sh
patching file arch/i386/boot/compressed/lzma_misc.c
patching file scripts/Makefile.lib

Applying linux-2.6.21.5-003-atmel.1-avr32-updates.patch using plaintext:
patching file MAINTAINERS
patching file Makefile
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file Makefile.rej

On Tue, 31 Jul 2007, Cristian Ionescu-Idbohrn wrote:

> Patch failed!  Please fix linux-2.6.21.5-003-atmel.1-avr32-updates.patch!
> make: *** [buildroot/build_i486/linux-2.6.21.5/.patched] Error 1

Conflicts between linux-2.6.21.5-002-lzma-vmlinuz.01.patch and
linux-2.6.21.5-003-atmel.1-avr32-updates.patch?


Cheers,

-- 
Cristian

  reply	other threads:[~2007-07-31 19:56 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 [this message]
2007-07-31 20:19   ` Cristian Ionescu-Idbohrn
2007-08-01  6:20     ` [Buildroot] linux-2.6.21.5-003-atmel.1-avr32-updates.patchfailes Ulf Samuelsson
2007-08-01 10:36     ` [Buildroot] linux-2.6.21.5-003-atmel.1-avr32-updates.patch failes 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=0707312154000.11633@somehost \
    --to=cristian.ionescu-idbohrn@axis.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.