All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kim Phillips <kim.phillips@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] lib_arch/board.c: Move malloc initialization before flash_init()
Date: Tue, 12 May 2009 15:09:11 -0500	[thread overview]
Message-ID: <20090512150911.8c1de6b0.kim.phillips@freescale.com> (raw)
In-Reply-To: <1242049812-6038-1-git-send-email-sr@denx.de>

On Mon, 11 May 2009 15:50:12 +0200
Stefan Roese <sr@denx.de> wrote:

> This patch moves the malloc initialization before calling flash_init().
> Upcoming changes to the NOR FLASH common CFI driver with optional
> MTD infrastructure and MTD concatenation support will call malloc().
> And nothing really speaks against enabling malloc just a little earlier
> in the boot stage. Some architectures already enable malloc before
> calling flash_init() so they don't need any changes here.
> 
> Signed-off-by: Stefan Roese <sr@denx.de>
> Cc: Wolfgang Denk <wd@denx.de>
> Cc: Mike Frysinger <vapier@gentoo.org>
> Cc: Scott McNutt <smcnutt@psyent.com>
> Cc: Shinya Kuribayashi <shinya.kuribayashi@necel.com>
> Cc: Nobuhiro Iwamatsu <iwamatsu@nigauri.org>
> Cc: Daniel Hellstrom <daniel@gaisler.com>
> Cc: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
> Cc: John Rigby <jcrigby@gmail.com>
> ---
> If nobody from the platforms custodians objects against this patch
> then I suggest that Wolfgang pulls it directly into next.

fyi, you've only cc:d Scott McNutt and John Rigby on this mail, yet you
indicate otherwise...

Kim

  reply	other threads:[~2009-05-12 20:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-11 13:50 [U-Boot] [PATCH] lib_arch/board.c: Move malloc initialization before flash_init() Stefan Roese
2009-05-12 20:09 ` Kim Phillips [this message]
2009-05-13  4:20   ` Stefan Roese
2009-05-13  4:58     ` Mike Frysinger
2009-05-13 15:55       ` Kim Phillips
2009-05-13  8:58     ` Detlev Zundel
2009-05-15 19:50 ` Wolfgang Denk

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=20090512150911.8c1de6b0.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.