public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: khilman@ti•com (Kevin Hilman)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] ARM: OMAP3: clockdomain: fix accidental duplicate registration
Date: Thu, 12 Jul 2012 10:50:13 -0700	[thread overview]
Message-ID: <87394wg97u.fsf@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1207120448120.25585@utopia.booyaka.com> (Paul Walmsley's message of "Thu, 12 Jul 2012 04:54:49 -0600 (MDT)")

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.
>
> Reported-by: Joe Woodward <jw@terrafix•co.uk>
> Cc: Tony Lindgren <tony@atomide•com>
> Cc: Kevin Hilman <khilman@ti•com>
> Signed-off-by: Paul Walmsley <paul@pwsan•com>

Acked-by: Kevin Hilman <khilman@ti•com>

This fixes the problem I reported here:

     http://marc.info/?l=linux-omap&m=134203768012711&w=2

Thanks,

Kevin

  reply	other threads:[~2012-07-12 17:50 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 [this message]
2012-07-13  6:47   ` Tony Lindgren
2012-07-14  8:52     ` Tony Lindgren
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=87394wg97u.fsf@ti.com \
    --to=khilman@ti$(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