From: Allen Martin <amartin@nvidia.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] arm: fix CONFIG_DELAY_ENVIRONMENT to act like it claims in the README
Date: Wed, 30 Jan 2013 16:34:59 -0800 [thread overview]
Message-ID: <20130131003459.GB18984@badger> (raw)
In-Reply-To: <20130131003142.GB3818@bill-the-cat>
On Wed, Jan 30, 2013 at 04:31:42PM -0800, Tom Rini wrote:
> * PGP Signed by an unknown key
>
> On Wed, Jan 30, 2013 at 03:04:53PM -0800, Allen Martin wrote:
> > On Tue, Jan 22, 2013 at 06:12:47AM -0800, Simon Glass wrote:
> > > On Tue, Jan 22, 2013 at 2:15 AM, Lucas Stach <dev@lynxeye.de> wrote:
> > > > No one expects to end up in a delayed environment if
> > > > CONFIG_DELAY_ENVIRONMENT isn't defined.
> > > >
> > > > Signed-off-by: Lucas Stach <dev@lynxeye.de>
> > >
> > > Good with me, and solves the immediate problem. Thanks for doing the patch.
> > >
> > > Acked-by: Simon Glass <sjg@chromium.org>
> > >
> >
> > Adding Tom Rini and Albert. What's the best way to get this up to
> > u-boot/master as quickly as possible? Environment is broken on all
> > boards that use fdt until this goes in.
>
> I can just grab this directly since everyone is happy. now.
>
That would be great, thanks!
-Allen
--
nvpublic
next prev parent reply other threads:[~2013-01-31 0:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 10:15 [U-Boot] [PATCH v2] arm: fix CONFIG_DELAY_ENVIRONMENT to act like it claims in the README Lucas Stach
2013-01-22 14:12 ` Simon Glass
2013-01-30 23:04 ` Allen Martin
2013-01-31 0:31 ` Tom Rini
2013-01-31 0:34 ` Allen Martin [this message]
2013-01-30 18:25 ` Allen Martin
2013-01-31 0:33 ` [U-Boot] [U-Boot, " Tom Rini
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=20130131003459.GB18984@badger \
--to=amartin@nvidia.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