From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] bump kernel headers to latest stable, including scsi patch for latests kernel headers
Date: Mon, 06 Sep 2010 10:03:01 +0200 [thread overview]
Message-ID: <87bp8bti2y.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <4C849D49.2040002@googlemail.com> (Marcus Osdoba's message of "Mon, 06 Sep 2010 09:50:33 +0200")
>>>>> "Marcus" == Marcus Osdoba <marcus.osdoba@googlemail.com> writes:
Hi,
Marcus> I'm using git of the current debian squeeze (which ist 1.7.1 or so). I
Marcus> used the built in git feature:
Marcus> git format-patch
Marcus> and
Marcus> git send-email with the formerly generated patch
And this was from an uptodate clone of the buildroot tree with no other
local changes?
Marcus> I have other patches in branch which introduce util-linux-ng. Can you
Marcus> give the output of the git am error?
git am -3 -s /tmp/linux.patch ~/source/buildroot
Applying: bump kernel headers to latest stable, including scsi patch for latests kernel headers
Using index info to reconstruct a base tree...
<stdin>:146: trailing whitespace.
<stdin>:157: space before tab in indent.
__be16 service_action;
<stdin>:158: space before tab in indent.
/* service specific data follows */
<stdin>:173: trailing whitespace.
<stdin>:174: trailing whitespace.
error: patch failed: toolchain/kernel-headers/linux-2.6.32.18-scsi-use-__uX-types-for-headers-exported-to-user-space.patch:1
error: toolchain/kernel-headers/linux-2.6.32.18-scsi-use-__uX-types-for-headers-exported-to-user-space.patch: patch does not apply
error: patch failed: toolchain/kernel-headers/linux-2.6.34.3-scsi-use-__uX-types-for-headers-exported-to-user-space.patch:1
error: toolchain/kernel-headers/linux-2.6.34.3-scsi-use-__uX-types-for-headers-exported-to-user-space.patch: patch does not apply
Did you hand edit your patch?
It does not apply to blobs recorded in its index.
Cannot fall back to three-way merge.
Patch failed at 0001 bump kernel headers to latest stable, including scsi patch for latests kernel headers
When you have resolved this problem run "git am -3 --resolved".
If you would prefer to skip this patch, instead run "git am -3 --skip".
To restore the original branch and stop patching run "git am -3 --abort".
I didn't see any obvious mangling of your patch (E.G. by your mailer),
but it doesn't like it.
Marcus> Does this patch
Marcus> (http://article.gmane.org/gmane.comp.lib.uclibc.buildroot/24766) cause
Marcus> the same error?
No, that one applies without problem.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2010-09-06 8:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-04 18:49 [Buildroot] [PATCH] bump kernel headers to latest stable, including scsi patch for latests kernel headers Marcus Osdoba
2010-09-04 20:36 ` Marcus Osdoba
2010-09-06 7:37 ` Peter Korsgaard
2010-09-06 7:50 ` Marcus Osdoba
2010-09-06 8:03 ` Peter Korsgaard [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=87bp8bti2y.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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