From: Tony Lindgren <tony@atomide.com>
To: Kevin Hilman <khilman@ti.com>
Cc: linux-omap <linux-omap@vger.kernel.org>,
"Mark A. Greer" <Mark.Greer@AnimalCreek.com>
Subject: Re: mismerge of 'omap-cleanup-for-v3.6' into tmp-merge
Date: Fri, 13 Jul 2012 00:00:07 -0700 [thread overview]
Message-ID: <20120713070007.GL1122@atomide.com> (raw)
In-Reply-To: <20120713064349.GH1122@atomide.com>
* Tony Lindgren <tony@atomide.com> [120712 23:48]:
> * Kevin Hilman <khilman@ti.com> [120711 13:15]:
> > Hi Tony,
> >
> > In your current master branch, commit 3dd50d054 (Merge tag
> > 'omap-cleanup-for-v3.6' into tmp-merge) added back the mpu_3xxx_clkdm
> > into the common clockdomains that was removed by commit 16e5e2c47 (ARM:
> > OMAP AM35x: clockdomain data: Fix clockdomain dependencies)
> >
> > This causes duplicate registration attempts for mpu_clkdm and the second
> > registration causes a warning from the clockdomain layer:
> >
> > clockdomain: mpu_clkdm: powerdomain ({Z�\x18ׂ� does not exist
>
> OK. Can you please check if this issue is also in arm-soc for-next
> and provide a patch if that's the case?
Oh looks like Paul already sent a fix for this one as
"[PATCH] ARM: OMAP3: clockdomain: fix accidental duplicate".
Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2012-07-13 7:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-11 20:10 mismerge of 'omap-cleanup-for-v3.6' into tmp-merge Kevin Hilman
2012-07-13 6:43 ` Tony Lindgren
2012-07-13 7:00 ` 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=20120713070007.GL1122@atomide.com \
--to=tony@atomide.com \
--cc=Mark.Greer@AnimalCreek.com \
--cc=khilman@ti.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).