From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Do we really need CONFIG_ARCH_CPU_INIT ?
Date: Fri, 2 Mar 2012 08:19:38 +0100 [thread overview]
Message-ID: <201203020819.38058.sr@denx.de> (raw)
In-Reply-To: <201203011448.13128.marek.vasut@gmail.com>
On Thursday 01 March 2012 14:48:12 Marek Vasut wrote:
> > ,so that CONFIG_ARCH_CPU_INIT is not needed anymore.
> >
> > Before I go further in this route to remove CONFIG_ARCH_CPU_INIT from
> > other places, I would like to know if this makes sense.
>
> I'm all for this.
Me too.
Thanks,
Stefan
next prev parent reply other threads:[~2012-03-02 7:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 13:23 [U-Boot] Do we really need CONFIG_ARCH_CPU_INIT ? Fabio Estevam
2012-03-01 13:48 ` Marek Vasut
2012-03-02 7:19 ` Stefan Roese [this message]
2012-03-01 20:48 ` Albert ARIBAUD
2012-03-02 8:46 ` Christian Riesch
2012-03-02 9:41 ` Christian Riesch
2012-03-01 21:28 ` Simon Glass
2012-03-01 22:19 ` Graeme Russ
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=201203020819.38058.sr@denx.de \
--to=sr@denx.de \
--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