From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: poky@yoctoproject.org
Subject: Re: [PATCH 0/1] remove u-boot flashing instructions for mpc8315e-rdb
Date: Thu, 31 Mar 2011 15:38:00 +0100 [thread overview]
Message-ID: <1301582280.24596.111.camel@rex> (raw)
In-Reply-To: <cover.1301578942.git.paul.eggleton@linux.intel.com>
On Thu, 2011-03-31 at 14:46 +0100, Paul Eggleton wrote:
> From: Paul Eggleton <paul.eggleton@linux.intel.com>
>
> Upgrading u-boot is apparently not necessary with current board revisions,
> and these instructions may not work properly anyway (our toolchain seems not
> to be able to compile u-boot in the way described), and given that they are
> potentially risky they should be removed.
>
> Pull URL: git://git.openembedded.org/openembedded-core-contrib
> Branch: paule/readme-hardware-fix3
> Browse: http://git.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/readme-hardware-fix3
>
> Thanks,
> Paul Eggleton <paul.eggleton@linux.intel.com>
> ---
>
>
> Paul Eggleton (1):
> README.hardware: remove u-boot flashing instructions for mpc8315e-rdb
Merged to master, thanks.
Richard
prev parent reply other threads:[~2011-03-31 14:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 13:46 [PATCH 0/1] remove u-boot flashing instructions for mpc8315e-rdb Paul Eggleton
2011-03-31 13:46 ` [PATCH 1/1] README.hardware: " Paul Eggleton
2011-03-31 14:19 ` [poky] " Wolfgang Denk
2011-03-31 14:23 ` Bruce Ashfield
2011-03-31 14:45 ` Wolfgang Denk
2011-03-31 16:32 ` Darren Hart
2011-03-31 21:31 ` Wolfgang Denk
2011-03-31 22:18 ` Darren Hart
2011-03-31 16:27 ` Darren Hart
2011-03-31 14:38 ` Richard Purdie [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=1301582280.24596.111.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=poky@yoctoproject.org \
/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