From: Kalle Valo <kalle.valo@iki.fi>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap@vger.kernel.org, tony@atomide.com
Subject: Re: n800 build error in clock24xx.c: 'secure_32k_ck' undeclared
Date: Thu, 23 Apr 2009 18:37:24 +0300 [thread overview]
Message-ID: <87eivjbcuj.fsf@litku.valot.fi> (raw)
In-Reply-To: <alpine.DEB.2.00.0904201141380.13457@utopia.booyaka.com> (Paul Walmsley's message of "Mon\, 20 Apr 2009 11\:47\:04 -0600 \(MDT\)")
Paul Walmsley <paul@pwsan.com> writes:
> Hi Kalle,
Hi Paul,
sorry for a late answer.
> On Fri, 17 Apr 2009, Kalle Valo wrote:
>
>> arch/arm/mach-omap2/clock24xx.h:1801: error: 'secure_32k_ck'
>> undeclared here (not in a function)
>>
>> Any hints?
>
> This is a bug in the version of fa9ef57a1efdd4e7c41a42db71d99b9b69e9b356 I
> pushed. The new clock definition in clock24xx.h for "secure_32k_fck"
> should be for "secure_32k_ck". Just talked with Tony about this; he's
> going to re-pull a fixed version of that patch today.
I updated to latest linux-omap (commit 55b1274c). It now compiles and
boots on N800.
Thank you for fixing this.
--
Kalle Valo
prev parent reply other threads:[~2009-04-23 15:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-17 20:44 n800 build error in clock24xx.c: 'secure_32k_ck' undeclared Kalle Valo
2009-04-19 5:00 ` green
2009-04-19 15:58 ` Kalle Valo
2009-04-20 1:23 ` green
2009-04-20 17:38 ` Tony Lindgren
2009-04-20 17:47 ` Paul Walmsley
2009-04-20 17:56 ` Paul Walmsley
2009-04-20 18:06 ` [APPLIED] n800 build error in clock24xx.c: 'secure_32k_ck' undeclared Tony Lindgren
2009-04-23 15:37 ` Kalle Valo [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=87eivjbcuj.fsf@litku.valot.fi \
--to=kalle.valo@iki.fi \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=tony@atomide.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