From: Kim Phillips <kim.phillips@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [u-boot] MPC8360E ATM Quad OC3 External Phys u-boot patch
Date: Mon, 11 Oct 2010 18:43:24 -0500 [thread overview]
Message-ID: <20101011184324.ebfbbcd3.kim.phillips@freescale.com> (raw)
In-Reply-To: <BB8FD0D817D3FC43B36C5D7C1C502EAA0209CAF5@zuk35exm20.fsl.freescale.net>
On Mon, 11 Oct 2010 15:41:44 +0100
Popa Stefan-R89990 <R89990@freescale.com> wrote:
Hello Stefan Popa,
> Attached you can find the patch for it.
It doesn't apply:
$ git am 358
Patch is empty. Was it split wrong?
If you would prefer to skip this patch, instead run "git am --skip".
To restore the original branch and stop patching run "git am --abort".
$ patch -p1 < 358
patch: **** Only garbage was found in the patch input.
$
Most likely because it's an attachment, which also makes reviewing with
inline responses more difficult: please re-review the instructions on
how to submit a patch:
http://www.denx.de/wiki/U-Boot/Patches
and resubmit.
Thanks,
Kim
prev parent reply other threads:[~2010-10-11 23:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-11 14:41 [U-Boot] [u-boot] MPC8360E ATM Quad OC3 External Phys u-boot patch Popa Stefan-R89990
2010-10-11 23:43 ` Kim Phillips [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=20101011184324.ebfbbcd3.kim.phillips@freescale.com \
--to=kim.phillips@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox