From: Ben Warren <biggerbadderben@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/3] Changed PPC4xx EMAC driver to require CONFIG_PPC4xx_EMAC
Date: Fri, 31 Oct 2008 16:03:14 -0700 [thread overview]
Message-ID: <490B8EB2.9060604@gmail.com> (raw)
In-Reply-To: <200810311116.11086.sr@denx.de>
Hi Stefan,
Stefan Roese wrote:
> Hi Ben,
>
> On Thursday 30 October 2008, Ben Warren wrote:
>
>> All in-tree IBM/AMCC PPC4xx boards using the EMAC get this new CONFIG
>>
>
> Looks good, thanks for all this work.
>
> Unfortunately it doesn't apply to my current u-boot-ppc4xx/master branch:
>
> [stefan at kubuntu u-boot-ppc4xx (master)]$ git am -3 -s patches_ben/\[PATCH\
> 1_3\]\ Changed\ PPC4xx\ EMAC\ driver\ to\ require\ CONFIG_PPC4xx_EMAC.mbox
> Applying: Changed PPC4xx EMAC driver to require CONFIG_PPC4xx_EMAC
> error: patch failed: net/eth.c:153
> error: net/eth.c: patch does not apply
> fatal: sha1 information is lacking or useless (net/eth.c).
> Repository lacks necessary blobs to fall back on 3-way merge.
> Cannot fall back to three-way merge.
> Patch failed at 0001.
> 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".
>
>
Yeah, I probably should have grouped all the net/eth.c patches
together. If you install the other ones sent at the same time I expect
it will apply. I'll re-base this one for you so you can test it.
> Could you please rebase it for me?
>
> And how should we handle these patches? Should they go in via my repository?
>
>
I was hoping you'd ACK them and I'd apply to -net, since it's but one of
many controllers I'm messing with.
> Best regards,
> Stefan
>
> =====================================================================
> DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
> =====================================================================
>
next prev parent reply other threads:[~2008-10-31 23:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 5:56 [U-Boot] [PATCH 1/3] Changed PPC4xx EMAC driver to require CONFIG_PPC4xx_EMAC Ben Warren
2008-10-30 5:56 ` [U-Boot] [PATCH 2/3] Moved PPC4xx EMAC driver to drivers/net Ben Warren
2008-10-30 5:56 ` [U-Boot] [PATCH 3/3] Moved initialization of PPC4xx EMAC to cpu_eth_init() Ben Warren
2008-10-31 10:16 ` [U-Boot] [PATCH 1/3] Changed PPC4xx EMAC driver to require CONFIG_PPC4xx_EMAC Stefan Roese
2008-10-31 23:03 ` Ben Warren [this message]
2008-11-03 7:53 ` Stefan Roese
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=490B8EB2.9060604@gmail.com \
--to=biggerbadderben@gmail.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