public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chen Gang <gang.chen@asianux.com>
To: Will Deacon <will.deacon@arm.com>
Cc: Jonathan Austin <Jonathan.Austin@arm.com>,
	Russell King - ARM Linux <linux@arm.linux.org.uk>,
	Lorenzo Pieralisi <Lorenzo.Pieralisi@arm.com>,
	Santosh Shilimkar <santosh.shilimkar@ti.com>,
	"nico@linaro.org" <nico@linaro.org>,
	Catalin Marinas <Catalin.Marinas@arm.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [Suggestion] Latest randconfig build errors for CONFIG_MMU=no
Date: Mon, 18 Mar 2013 09:41:24 +0800	[thread overview]
Message-ID: <514670C4.8010801@asianux.com> (raw)
In-Reply-To: <20130317144030.GF19071@mudshark.cambridge.arm.com>

On 2013年03月17日 22:40, Will Deacon wrote:
> I can probably bring that up to speed with -rc2 if people are interested.
> The tricky part is testing -- I used a software model that had a magic
> control block for killing off CPUs when I wrote this originally.

  excuse me, I am not familiar with ARM, so can not provide more ideas.

  but at least for me, I think what you said seems valuable.

  welcome any ARM experts to reply.


  thanks.

  :-)


-- 
Chen Gang

Asianux Corporation

      reply	other threads:[~2013-03-18  1:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-14  3:44 [Suggestion] Latest randconfig build errors for CONFIG_MMU=no Chen Gang
2013-03-14  3:46 ` Chen Gang
2013-03-14 13:25 ` Jonathan Austin
2013-03-15  0:51   ` Chen Gang
2013-03-17 14:40   ` Will Deacon
2013-03-18  1:41     ` Chen Gang [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=514670C4.8010801@asianux.com \
    --to=gang.chen@asianux.com \
    --cc=Catalin.Marinas@arm.com \
    --cc=Jonathan.Austin@arm.com \
    --cc=Lorenzo.Pieralisi@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=nico@linaro.org \
    --cc=santosh.shilimkar@ti.com \
    --cc=will.deacon@arm.com \
    /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