From: Tony Lindgren <tony@atomide.com>
To: balrogg@gmail.com
Cc: Linux-OMAP <linux-omap-open-source@linux.omap.com>
Subject: Re: [PATCH] ARM: OMAP: correct misc 15xx and non-15xx platform code
Date: Thu, 28 Sep 2006 16:58:50 +0300 [thread overview]
Message-ID: <20060928135849.GI29453@atomide.com> (raw)
In-Reply-To: <fb249edb0609221301u6fc66d0ci51ddf77449a2656f@mail.gmail.com>
* andrzej zaborowski <balrog@zabor.org> [060922 23:02]:
> Disable accesses to SOFT_REQ_REG2 and ULPD_SOFT_DISABLE_REQ_REG
> registers for 15xx processors that don't have these registers. Enable
> level 2 interrupt handler for processors that identify as OMAP 15xx
> (e.g 310) and not 1510 specifically. Also fix the following compiler
> warning (only visible with CONFIG_OMAP_RESET_CLOCKS):
>
> arch/arm/mach-omap1/clock.c: In function 'omap1_clk_disable_unused':
> arch/arm/mach-omap1/clock.c:634: warning: 'return' with a value, in
> function returning void
>
> Signed-off-by: Andrzej Zaborowski <balrog@zabor.org>
Pushing today.
Tony
prev parent reply other threads:[~2006-09-28 13:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-22 20:01 [PATCH] ARM: OMAP: correct misc 15xx and non-15xx platform code andrzej zaborowski
2006-09-28 13:58 ` Tony Lindgren [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=20060928135849.GI29453@atomide.com \
--to=tony@atomide.com \
--cc=balrogg@gmail.com \
--cc=linux-omap-open-source@linux.omap.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.