From: tony@atomide•com (Tony Lindgren)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] ARM: OMAP3: clockdomain: fix accidental duplicate registration
Date: Sat, 14 Jul 2012 01:52:58 -0700 [thread overview]
Message-ID: <20120714085257.GB6522@atomide.com> (raw)
In-Reply-To: <20120713064713.GI1122@atomide.com>
* Tony Lindgren <tony@atomide•com> [120712 23:52]:
> * Kevin Hilman <khilman@ti•com> [120712 10:55]:
> > Paul Walmsley <paul@pwsan•com> writes:
> >
> > > Commit 3dd50d0545bd5a8ad83d4339f07935cd3e883271 ("Merge tag
> > > 'omap-cleanup-for-v3.6' into tmp-merge") inadvertently caused a
> > > clockdomain to be registered twice on OMAP3 boards. This causes warnings
> > > on boot, wild pointer dereferences, and PM regressions. Fix the double
> > > registration and add some clockdomain code to prevent this from happening
> > > again.
As the tmp-merge branch has other branches and never goes upstream, the
commit should say:
Commit 472fd5401561f94698f4c8f9dbbbfbf76ab55626 (Merge branch 'cleanup-hwmod'
into cleanup)... So I've updated the patch and applied it into l-o master.
The patch seems to produce a new warning against arm soc tree next/cleanup
branch:
warning: ?mpu_3xxx_clkdm? defined but not used
Paul, care to check if a change is needed for the arm soc tree
next/cleanup branch version of this patch?
Tony
next prev parent reply other threads:[~2012-07-14 8:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-12 10:54 [PATCH] ARM: OMAP3: clockdomain: fix accidental duplicate registration Paul Walmsley
2012-07-12 17:50 ` Kevin Hilman
2012-07-13 6:47 ` Tony Lindgren
2012-07-14 8:52 ` Tony Lindgren [this message]
2012-07-14 17:54 ` Paul Walmsley
2012-07-16 8:36 ` Tony Lindgren
2012-07-18 9:53 ` Paul Walmsley
2012-07-19 11:52 ` Tony Lindgren
2012-07-19 19:12 ` Paul Walmsley
2012-07-24 8:16 ` Tony Lindgren
2012-07-24 20:52 ` Paul Walmsley
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=20120714085257.GB6522@atomide.com \
--to=tony@atomide$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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