From: Sam Ravnborg <sam@ravnborg.org>
To: Len Brown <lenb@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Len Brown <len.brown@intel.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
sparclinux@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the final tree (acpi tree related)
Date: Tue, 12 Feb 2013 18:35:06 +0100 [thread overview]
Message-ID: <20130212173505.GA2155@merkur.ravnborg.org> (raw)
In-Reply-To: <51197D8B.6010407@kernel.org>
> > Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
> > ---
> > arch/sparc/include/asm/processor.h | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/arch/sparc/include/asm/processor.h b/arch/sparc/include/asm/processor.h
> > index 34baa35..622cfa5 100644
> > --- a/arch/sparc/include/asm/processor.h
> > +++ b/arch/sparc/include/asm/processor.h
> > @@ -7,6 +7,8 @@
> > #endif
> >
> > #define nop() __asm__ __volatile__ ("nop")
> > +#ifndef __ASSEMBLY__
> > extern void (*sparc_idle)(void);
> > +#endif
> >
> > #endif
> >
>
> Thank you Stephen!
>
> The last time I compiled a sparc kernel was in 1993:-)
>
> I've added your fix and Dave's Ack to this patch,
> and updated it in my next branch.
Hi Len.
Can you please move the definition of sparc_idle to processor_32.h
It is sparc32 specific - and then we do not need the __ASSEMBLY__ guards
as the sparc32 variant are not used from assembler.
Do you btw. have any hints how I can convert to the cpu_idle thing you hinted?
Sam
next prev parent reply other threads:[~2013-02-12 17:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 7:34 Stephen Rothwell
2013-02-11 18:22 ` Bjorn Helgaas
2013-02-11 23:23 ` Len Brown
2013-02-12 17:35 ` Sam Ravnborg [this message]
2013-02-12 18:01 ` Should SPARC use cpuidle? (was: linux-next: build failure after merge of the final tree (acpi tree related)) Len Brown
2013-02-12 18:03 ` Should SPARC use cpuidle? Len Brown
2013-02-12 19:36 ` Sam Ravnborg
2013-02-12 19:42 ` Should SPARC use cpuidle? (was: linux-next: build failure after merge of the final tree (acpi tree related)) Sam Ravnborg
-- strict thread matches above, loose matches on Subject: below --
2010-05-24 3:41 linux-next: build failure after merge of the final tree (acpi tree related) Stephen Rothwell
2010-05-24 6:31 ` Len Brown
2010-05-24 7:41 ` Stephen Rothwell
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=20130212173505.GA2155@merkur.ravnborg.org \
--to=sam@ravnborg.org \
--cc=davem@davemloft.net \
--cc=len.brown@intel.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=sparclinux@vger.kernel.org \
/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®