public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Ron Madrid <ron_madrid@sbcglobal.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mpc83xx: Size optimization of start.S
Date: Thu, 22 Jan 2009 10:00:56 -0800 (PST)	[thread overview]
Message-ID: <486452.48937.qm@web83503.mail.sp1.yahoo.com> (raw)
In-Reply-To: <20090121185551.73f41683.kim.phillips@freescale.com>

No worries.  With the holidays and all I figured that it was just delayed.

Since my new board patch is dependent on this being applied is it possible to now resubmit my new board patch?

Thanks.

Ron


--- On Wed, 1/21/09, Kim Phillips <kim.phillips@freescale.com> wrote:

> From: Kim Phillips <kim.phillips@freescale.com>
> Subject: Re: [U-Boot] [PATCH] mpc83xx: Size optimization of start.S
> To: "Ron Madrid" <ron_madrid@sbcglobal.net>
> Cc: u-boot at lists.denx.de
> Date: Wednesday, January 21, 2009, 4:55 PM
> On Fri, 12 Dec 2008 13:12:45 -0800
> Ron Madrid <ron_madrid@sbcglobal.net> wrote:
> 
> > Currently there are in excess of 100 bytes located at
> the beginning of the image
> > built by start.S that are not being utilized.  This
> patch moves a few functions
> > into this part of the image.  This will create a
> greater number of *available*
> > bytes that can be used by board specific code in NAND
> builds and will decrease
> > the size of the assembled code in other builds.
> > 
> > Signed-off-by: Ron Madrid
> <ron_madrid@sbcglobal.net>
> > ---
> 
> applied to u-boot-mpc83xx next.
> 
> Thanks, and sorry for the delay,
> 
> Kim

  reply	other threads:[~2009-01-22 18:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-12 21:12 [U-Boot] [PATCH] mpc83xx: Size optimization of start.S Ron Madrid
2008-12-15  7:26 ` Jens Gehrlein
2008-12-15 17:00   ` Scott Wood
2008-12-16  7:58     ` Jens Gehrlein
2009-01-12 18:52 ` Ron Madrid
2009-01-22  0:55 ` Kim Phillips
2009-01-22 18:00   ` Ron Madrid [this message]
2009-01-22 18:37     ` Kim Phillips
2009-01-22 21:37       ` Ron Madrid
2009-01-22 22:32         ` Kim Phillips

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=486452.48937.qm@web83503.mail.sp1.yahoo.com \
    --to=ron_madrid@sbcglobal.net \
    --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