* Paul Walmsley p...@pwsan.com [120719 12:17]:
On Thu, 19 Jul 2012, Tony Lindgren wrote:
Well I'm still a bit confused :)
Which branch in arm-soc tree should this fix be applied then?
In terms of arm-soc, it's needed in arm-soc for-next, due to commit
On Tue, 24 Jul 2012, Tony Lindgren wrote:
OK looks like Linus fixed up part of it, care to check what's needed
against current mainline now?
Current mainline seems to be okay here.
- Paul
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to
* Paul Walmsley p...@pwsan.com [120718 02:58]:
Hi
On Mon, 16 Jul 2012, Tony Lindgren wrote:
Hmm well it seems that we should apply this fix into arm-soc next/cleanup
branch if that's where the mismerge happened? It seems the same mismerge
is there even without 16e5e2c4?
The arm-soc
On Thu, 19 Jul 2012, Tony Lindgren wrote:
Well I'm still a bit confused :)
Which branch in arm-soc tree should this fix be applied then?
In terms of arm-soc, it's needed in arm-soc for-next, due to commit
066b6eba6d58ad1cb9ec3917b6ee79730c3c3310 (Merge branch 'next/cleanup'
into for-next).
Hi
On Mon, 16 Jul 2012, Tony Lindgren wrote:
Hmm well it seems that we should apply this fix into arm-soc next/cleanup
branch if that's where the mismerge happened? It seems the same mismerge
is there even without 16e5e2c4?
The arm-soc next/cleanup copy of mach-omap2/clockdomains3xxx_data.c
* Paul Walmsley p...@pwsan.com [120714 10:59]:
On Sat, 14 Jul 2012, Tony Lindgren wrote:
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
* Tony Lindgren t...@atomide.com [120712 23:52]:
* Kevin Hilman khil...@ti.com [120712 10:55]:
Paul Walmsley p...@pwsan.com writes:
Commit 3dd50d0545bd5a8ad83d4339f07935cd3e883271 (Merge tag
'omap-cleanup-for-v3.6' into tmp-merge) inadvertently caused a
clockdomain to be
On Sat, 14 Jul 2012, Tony Lindgren wrote:
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.
* Kevin Hilman khil...@ti.com [120712 10:55]:
Paul Walmsley p...@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