From: Antony Pavlov <antonynpavlov@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [RFC 0/3] MIPS: add the initial support for lowlevel init
Date: Mon, 14 May 2012 12:28:28 +0400 [thread overview]
Message-ID: <CAA4bVAHAn3aiB1d6KnJ_LhmnKje_DWn8vrW4RcCVnMgEBXvbcQ@mail.gmail.com> (raw)
In-Reply-To: <20120514081846.GE21318@pengutronix.de>
On 14 May 2012 12:18, Sascha Hauer <s.hauer@pengutronix.de> wrote:
> On Sun, May 13, 2012 at 09:24:41PM +0400, Antony Pavlov wrote:
>> This patch series introduce the initial support for lowlevel init
>> for the MIPS boards.
>>
>> In the future low level initialization will be used
>> for cache initialization.
>>
>> [RFC 1/3] MIPS: move start.S code to .text_entry section
>> [RFC 2/3] MIPS: add the initial support for lowlevel init
>> [RFC 3/3] MIPS: malta: add bogus lowlevel init
>
> Looks mostly good except that you have some whitespace damage in your
> patches.
Hmm. checkpatch.pl didn't find anything. Can you give any sample, please.
> Can we drop 3/3 until we have something useful in the lowlevel
> init?
Just now I'm working on cache support for MIPS. I think we can get
useful in the lowlevel init in a few days :))
--
Best regards,
Antony Pavlov
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2012-05-14 8:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-13 17:24 Antony Pavlov
2012-05-13 17:24 ` [RFC 1/3] MIPS: move start.S code to .text_entry section Antony Pavlov
2012-05-13 17:24 ` [RFC 2/3] MIPS: add the initial support for lowlevel init Antony Pavlov
2012-05-14 8:55 ` Sascha Hauer
2012-05-14 9:13 ` Antony Pavlov
2012-05-13 17:24 ` [RFC 3/3] MIPS: malta: add bogus " Antony Pavlov
2012-05-14 8:18 ` [RFC 0/3] MIPS: add the initial support for " Sascha Hauer
2012-05-14 8:28 ` Antony Pavlov [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=CAA4bVAHAn3aiB1d6KnJ_LhmnKje_DWn8vrW4RcCVnMgEBXvbcQ@mail.gmail.com \
--to=antonynpavlov@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.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