Skip to contentSkip to conversation

OK to use commit 71856843 as base for further omap clean up?

DISCUSSION Tony Lindgren 3 participants 5 messages Mar 19, 2013 – Apr 3, 2013

lore
Share & tools
lore
#0 lore raw

Hi Russell,

Can we use your commit 71856843 (ARM: OMAP: use consistent error checking) as an immutable base for further omap dmtimer and gpmc work?

Regards,

Tony

#2 lore raw
Quoted 10 lines · Jon Hunter

Hi Russell,

Quoted 4 lines · Tony Lindgren

Hi Russell,

Can we use your commit 71856843 (ARM: OMAP: use consistent error checking) as an immutable base for further omap dmtimer and gpmc work?

I saw that you updated your clean-up branch. Ok to use the below commit
[1] as a base for some v3.10 updates?

It's still the same commit. I'm not intending to remove this commit from it, so yes, fine, go ahead.

#3 lore raw
Quoted 6 lines · Russell King - ARM Linux
Quoted 5 lines · Jon Hunter

Hi Russell,

Quoted 2 lines · Tony Lindgren

Hi Russell,

Quoted 8 lines
Quoted 5 lines
Quoted 2 lines

Can we use your commit 71856843 (ARM: OMAP: use consistent error checking) as an immutable base for further omap dmtimer and gpmc work?

I saw that you updated your clean-up branch. Ok to use the below commit
[1] as a base for some v3.10 updates?

It's still the same commit. I'm not intending to remove this commit from it, so yes, fine, go ahead.

*sigh*. Actually, 4d485661d799e81f98097057d445f4803cef2af0 is buggered which is the commit below it. I said yes too quickly. Oh well, it'll just have to be broken for when it hits mainline now.

#4 lore raw
Quoted 13 lines · Russell King - ARM Linux
Quoted 12 lines · Russell King - ARM Linux
Quoted 10 lines · Jon Hunter

Hi Russell,

Quoted 4 lines · Tony Lindgren

Hi Russell,

Can we use your commit 71856843 (ARM: OMAP: use consistent error checking) as an immutable base for further omap dmtimer and gpmc work?

I saw that you updated your clean-up branch. Ok to use the below commit
[1] as a base for some v3.10 updates?

Quoted 6 lines
Quoted 2 lines

It's still the same commit. I'm not intending to remove this commit from it, so yes, fine, go ahead.

*sigh*. Actually, 4d485661d799e81f98097057d445f4803cef2af0 is buggered which is the commit below it. I said yes too quickly. Oh well, it'll just have to be broken for when it hits mainline now.

Yes we have few branches based on that. Note that the issue reported by Lothar I just resolved in the omap-for-v3.10/timer branch along with other conflicts when pulling in Jon's patches, so that might do the trick assuming there are no other issues.

Regards,

Tony