From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH v3] QE IO: Add initial data to pin configuration + read/write functions
Date: Wed, 23 Jan 2008 16:43:20 -0600 [thread overview]
Message-ID: <4797C308.6030106@freescale.com> (raw)
In-Reply-To: <B27D27F93BC429468DBC3B0DA043AA4401C65D50@ilptex01.ecitele.com>
David Saada wrote:
> No problem. If there's nothing else, I'll repost the patch with this
> change (hopefully the last time).
> I also implemented commands for reading and writing parallel I/O (pario
> read/write), but I'll post this as a separate patch.
> David.
I still can't apply the patch:
$ git-am "/home/b04825/.mozilla/default/2ir4ayuy.slt/Mail/Local Folders/patches"
Applying QE IO: Add initial data to pin configuration + read/write functions
fatal: corrupt patch at line 40
Patch failed at 0001.
When you have resolved this problem run "git-am --resolved".
If you would prefer to skip this patch, instead run "git-am --skip".
I see these in the message body:
+ int data;
} qe_iop_conf_t;
=20
#define QE_IOP_TAB_END (-1)
The "=20" is the problem. Have you tried using git-send-email?
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2008-01-23 22:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-17 14:31 [U-Boot-Users] [PATCH v2] QE IO: Add initial data to pin configuration + read/write functions David Saada
2008-01-17 17:30 ` Timur Tabi
2008-01-17 17:39 ` Timur Tabi
2008-01-20 6:48 ` David Saada
2008-01-20 9:36 ` [U-Boot-Users] [PATCH v3] " David Saada
2008-01-22 18:11 ` David Saada
2008-01-22 18:55 ` Timur Tabi
2008-01-23 7:47 ` David Saada
2008-01-23 22:43 ` Timur Tabi [this message]
2008-01-28 16:01 ` Timur Tabi
2008-01-28 16:21 ` David Saada
2008-02-05 16:54 ` Andy Fleming
2008-02-06 7:44 ` David Saada
2008-02-07 10:26 ` [U-Boot-Users] [PATCH v4] " David Saada
2008-02-07 15:28 ` Timur Tabi
2008-02-07 15:55 ` David Saada
2008-02-07 15:57 ` Timur Tabi
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=4797C308.6030106@freescale.com \
--to=timur@freescale.com \
--cc=u-boot@lists.denx.de \
/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.