"[-next] ARM: Fix build if CLKDEV_LOOKUP is not configured"

"[-next] ARM: Fix build if CLKDEV_LOOKUP is not configured"

[Russell King - ARM Linux]

If you'd like me to apply a patch, it's no good discussing it in a
place where I have no knowledge of, and then suggesting that I
should apply it.

Paul Gortmaker brought your patch to my attention, and said that it
had been breaking MIPS for a week, and asked whether I had any
knowledge of it.  I did not.

Given that the patch was created on 14th June, and it's now some 9
days later, I have to ask what's going on here?  Has someone else
queued it up?  Is someone intending to apply it during the merge
window once the stuff which causes the breakage in my tree has
landed?  Are you still expecting me to somehow pick up a patch that
I had no knowledge of, for a breakage that I had no knowledge of?

Basically, what are you expecting to happen with this patch?

-- 
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.

Re: "[-next] ARM: Fix build if CLKDEV_LOOKUP is not configured"

[Thomas Gleixner]

On Tue, 23 Jun 2015, Russell King - ARM Linux wrote:
> If you'd like me to apply a patch, it's no good discussing it in a
> place where I have no knowledge of, and then suggesting that I
> should apply it.
> 
> Paul Gortmaker brought your patch to my attention, and said that it
> had been breaking MIPS for a week, and asked whether I had any
> knowledge of it.  I did not.
> 
> Given that the patch was created on 14th June, and it's now some 9
> days later, I have to ask what's going on here?  Has someone else
> queued it up?  Is someone intending to apply it during the merge
> window once the stuff which causes the breakage in my tree has
> landed?  Are you still expecting me to somehow pick up a patch that
> I had no knowledge of, for a breakage that I had no knowledge of?
> 
> Basically, what are you expecting to happen with this patch?

Pick it up please. I ignored it when Sudeep said, that it should go
through your tree, of course w/o cc'ing you.

Guenter did not cc you probably because he thought it's wreckage
originating from the clocksource tree.

Thanks,

	tglx

Re: "[-next] ARM: Fix build if CLKDEV_LOOKUP is not configured"

[Guenter Roeck]

On Tue, Jun 23, 2015 at 05:49:19PM +0200, Thomas Gleixner wrote:
> On Tue, 23 Jun 2015, Russell King - ARM Linux wrote:
> > If you'd like me to apply a patch, it's no good discussing it in a
> > place where I have no knowledge of, and then suggesting that I
> > should apply it.
> > 
> > Paul Gortmaker brought your patch to my attention, and said that it
> > had been breaking MIPS for a week, and asked whether I had any
> > knowledge of it.  I did not.
> > 
> > Given that the patch was created on 14th June, and it's now some 9
> > days later, I have to ask what's going on here?  Has someone else
> > queued it up?  Is someone intending to apply it during the merge
> > window once the stuff which causes the breakage in my tree has
> > landed?  Are you still expecting me to somehow pick up a patch that
> > I had no knowledge of, for a breakage that I had no knowledge of?
> > 
> > Basically, what are you expecting to happen with this patch?
> 
> Pick it up please. I ignored it when Sudeep said, that it should go
> through your tree, of course w/o cc'ing you.
> 
> Guenter did not cc you probably because he thought it's wreckage
> originating from the clocksource tree.
> 
Sorry, I should have followed up. Too much on my plate :-(.
I hope I can resend it tonight with proper Cc:.

Guenter

Re: "[-next] ARM: Fix build if CLKDEV_LOOKUP is not configured"

[Sudeep Holla]

On 23/06/15 16:37, Russell King - ARM Linux wrote:
> If you'd like me to apply a patch, it's no good discussing it in a
> place where I have no knowledge of, and then suggesting that I should
> apply it.
>

Sorry for that, I agree but I just mentioned it should go via your tree
as other SP804 patches changing Kconfig was in your tree to avoid any
merge conflicts. I assumed you were copied, my mistake :(

> Paul Gortmaker brought your patch to my attention, and said that it
> had been breaking MIPS for a week, and asked whether I had any
> knowledge of it.  I did not.
>
> Given that the patch was created on 14th June, and it's now some 9
> days later, I have to ask what's going on here?  Has someone else
> queued it up?  Is someone intending to apply it during the merge
> window once the stuff which causes the breakage in my tree has
> landed?  Are you still expecting me to somehow pick up a patch that I
> had no knowledge of, for a breakage that I had no knowledge of?
>

Again I thought Guenter Roeck will stick this in your patch tracker ASAP.

> Basically, what are you expecting to happen with this patch?
>

I should have explicitly asked Guenter Roeck to put in your patch
tracker. Sorry for that.

Guenter,

Can you put this patch in RMK's patch tracker ?

Regards,
Sudeep