From: Paul Walmsley <paul@pwsan.com>
To: linux-omap@vger.kernel.org
Cc: linux-arm-kernel@lists.arm.linux.org.uk
Subject: [PATCH 0/2] OMAP clock and clockdomain fixes for 2.6.29-rc5
Date: Wed, 14 Oct 2009 16:31:35 -0600 [thread overview]
Message-ID: <20091014222609.5545.7736.stgit@localhost.localdomain> (raw)
Hello,
This series contains:
- one OMAP2 clock fix that allows N800 to boot further (there are unrelated
problems with both the current linux-omap head and omap-fixes branch that
cause booting to fail due to other reasons), and
- one OMAP2/3 clockdomain fix that can cause clockdomain transitions to be
missed by the clockdomain code -- this mostly affects OMAP3 OFF mode.
These patches are also available as a git branch (based on Tony's omap-fixes
branch) from
git://git.pwsan.com/linux-2.6 2_6_32rc4_fixes
- Paul
---
Kalle Jokiniemi (1):
OMAP: Fix race condition with autodeps
Paul Walmsley (1):
OMAP2xxx clock: set up clockdomain pointer in struct clk
arch/arm/mach-omap2/clock24xx.c | 1 +
arch/arm/mach-omap2/clockdomain.c | 74 ++++++++++++++++++++++---------------
2 files changed, 45 insertions(+), 30 deletions(-)
size:
text data bss dec hex filename
3588474 198624 105152 3892250 3b641a vmlinux.omap3beagle.orig
3588562 198624 105152 3892338 3b6472 vmlinux.omap3beagle.patched
WARNING: multiple messages have this Message-ID (diff)
From: paul@pwsan.com (Paul Walmsley)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] OMAP clock and clockdomain fixes for 2.6.29-rc5
Date: Wed, 14 Oct 2009 16:31:35 -0600 [thread overview]
Message-ID: <20091014222609.5545.7736.stgit@localhost.localdomain> (raw)
(resending due to old l-a-k host address)
Hello,
This series contains:
- one OMAP2 clock fix that allows N800 to boot further (there are unrelated
problems with both the current linux-omap head and omap-fixes branch that
cause booting to fail due to other reasons), and
- one OMAP2/3 clockdomain fix that can cause clockdomain transitions to be
missed by the clockdomain code -- this mostly affects OMAP3 OFF mode.
These patches are also available as a git branch (based on Linus'
v2.6.32-rc4 tag) from
git://git.pwsan.com/linux-2.6 2_6_32rc4_fixes
- Paul
---
Kalle Jokiniemi (1):
OMAP: Fix race condition with autodeps
Paul Walmsley (1):
OMAP2xxx clock: set up clockdomain pointer in struct clk
arch/arm/mach-omap2/clock24xx.c | 1 +
arch/arm/mach-omap2/clockdomain.c | 74 ++++++++++++++++++++++---------------
2 files changed, 45 insertions(+), 30 deletions(-)
size:
text data bss dec hex filename
3588474 198624 105152 3892250 3b641a vmlinux.omap3beagle.orig
3588562 198624 105152 3892338 3b6472 vmlinux.omap3beagle.patched
next reply other threads:[~2009-10-14 22:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-14 22:31 Paul Walmsley [this message]
2009-10-14 22:31 ` [PATCH 0/2] OMAP clock and clockdomain fixes for 2.6.29-rc5 Paul Walmsley
2009-10-14 22:31 ` [PATCH 1/2] OMAP: Fix race condition with autodeps Paul Walmsley
2009-10-14 22:31 ` [PATCH 2/2] OMAP2xxx clock: set up clockdomain pointer in struct clk Paul Walmsley
2009-10-14 22:31 ` Paul Walmsley
2009-10-14 23:30 ` [PATCH 0/2] OMAP clock and clockdomain fixes for 2.6.29-rc5 Paul Walmsley
2009-10-14 23:30 ` Paul Walmsley
2009-10-15 0:24 ` Tony Lindgren
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=20091014222609.5545.7736.stgit@localhost.localdomain \
--to=paul@pwsan.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-omap@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 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.