From: Will Deacon <will.deacon@arm.com>
To: Jonathan Austin <Jonathan.Austin@arm.com>
Cc: Chen Gang <gang.chen@asianux.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: Sun, 17 Mar 2013 14:40:30 +0000 [thread overview]
Message-ID: <20130317144030.GF19071@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <5141CFE4.2030909@arm.com>
On Thu, Mar 14, 2013 at 01:25:56PM +0000, Jonathan Austin wrote:
> On 14/03/13 03:44, Chen Gang wrote:
> > Hello Maintainers:
> >
> > when use randconfig:
> > make V=1 EXTRA_CFLAGS=-W ARCH=arm randconfig
> > (and "grep CONFIG_MMU .config" outputs "# CONFIG_MMU is not set")
> >
> > the error information:
> > arch/arm/kernel/suspend.c: 在函数‘cpu_suspend’中:
> > arch/arm/kernel/suspend.c:56:32: 错误：提领指向不完全类型的指针
> > arch/arm/kernel/suspend.c:70:3: 错误：隐式声明函数‘cpu_switch_mm’ [-Werror=implicit-function-declaration]
> > arch/arm/kernel/suspend.c:71:3: 错误：隐式声明函数‘local_flush_bp_all’ [-Werror=implicit-function-declaration]
> > arch/arm/kernel/suspend.c:72:3: 错误：隐式声明函数‘local_flush_tlb_all’ [-Werror=implicit-function-declaration]
> >
> > I want to be sure whether we can bear it ?
> >
>
> You're right that at the moment that suspend code is broken for NOMMU.
>
> However, Will Deacon has a patch to fix it in his nommu branch on
> kernel.org:
>
> https://git.kernel.org/cgit/linux/kernel/git/will/linux.git/commit/?h=nommu
>
> I'll let Will comment on how/when he might look at proposing that code
> to be merged.
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.
Will
next prev parent reply other threads:[~2013-03-17 14:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 3:44 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 [this message]
2013-03-18 1:41 ` Chen Gang
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=20130317144030.GF19071@mudshark.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=Catalin.Marinas@arm.com \
--cc=Jonathan.Austin@arm.com \
--cc=Lorenzo.Pieralisi@arm.com \
--cc=gang.chen@asianux.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 \
/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
all inboxes | Powered by JetHome®