* Re: KVM: CONFIG_LOCK_DEP and CONFIG_LOCK_DETECTOR?
@ 2015-01-22 19:18 ` Marc Zyngier
0 siblings, 0 replies; 9+ messages in thread
From: Marc Zyngier @ 2015-01-22 19:18 UTC (permalink / raw)
To: Mario Smarduch, Paul Bolle
Cc: Valentin Rothberg, Christoffer Dall, Gleb Natapov, Paolo Bonzini,
Russell King, kvm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu, linux-kernel@vger.kernel.org
On 22/01/15 19:13, Mario Smarduch wrote:
> On 01/22/2015 01:34 AM, Paul Bolle wrote:
>> Mario,
>>
>> Your commit c64735554c0a ("KVM: arm: Add initial dirty page locking
>> support") is included in today's linux-next (ie, next-20150122). I
>> noticed because a script I use to check linux-next spotted a minor
>> problem with it.
>>
>> This commit added a comment that mentions CONFIG_LOCK_DEP and
>> CONFIG_LOCK_DETECTOR. It seems CONFIG_LOCKDEP and CONFIG_LOCKUP_DETECTOR
>> should be used instead. Is a trivial patch to fix these typos queued
>> somewhere?
>>
>> Thanks,
>>
>>
>> Paul Bolle
>>
>
> Hi Paul,
> thanks for spotting that. No there is no trivial patch
> queued, didn't notice it until now. Can I submit a follow
> up trivial patch later?
Yeah, that can definitely wait. I think we have slightly bigger fish to
fry for now... ;-)
If someone sends us a patch once -rc1 is out, we'll queue it.
Thanks,
M.
--
Jazz is not dead. It just smells funny...
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: KVM: CONFIG_LOCK_DEP and CONFIG_LOCK_DETECTOR?
@ 2015-01-22 19:18 ` Marc Zyngier
0 siblings, 0 replies; 9+ messages in thread
From: Marc Zyngier @ 2015-01-22 19:18 UTC (permalink / raw)
To: Mario Smarduch, Paul Bolle
Cc: Russell King, kvm@vger.kernel.org, Gleb Natapov,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, Paolo Bonzini,
kvmarm@lists.cs.columbia.edu, Christoffer Dall, Valentin Rothberg
On 22/01/15 19:13, Mario Smarduch wrote:
> On 01/22/2015 01:34 AM, Paul Bolle wrote:
>> Mario,
>>
>> Your commit c64735554c0a ("KVM: arm: Add initial dirty page locking
>> support") is included in today's linux-next (ie, next-20150122). I
>> noticed because a script I use to check linux-next spotted a minor
>> problem with it.
>>
>> This commit added a comment that mentions CONFIG_LOCK_DEP and
>> CONFIG_LOCK_DETECTOR. It seems CONFIG_LOCKDEP and CONFIG_LOCKUP_DETECTOR
>> should be used instead. Is a trivial patch to fix these typos queued
>> somewhere?
>>
>> Thanks,
>>
>>
>> Paul Bolle
>>
>
> Hi Paul,
> thanks for spotting that. No there is no trivial patch
> queued, didn't notice it until now. Can I submit a follow
> up trivial patch later?
Yeah, that can definitely wait. I think we have slightly bigger fish to
fry for now... ;-)
If someone sends us a patch once -rc1 is out, we'll queue it.
Thanks,
M.
--
Jazz is not dead. It just smells funny...
^ permalink raw reply [flat|nested] 9+ messages in thread* KVM: CONFIG_LOCK_DEP and CONFIG_LOCK_DETECTOR?
2015-01-22 19:18 ` Marc Zyngier
@ 2015-01-23 9:44 ` Christoffer Dall
-1 siblings, 0 replies; 9+ messages in thread
From: Christoffer Dall @ 2015-01-23 9:44 UTC (permalink / raw)
To: linux-arm-kernel
On Thu, Jan 22, 2015 at 07:18:25PM +0000, Marc Zyngier wrote:
> On 22/01/15 19:13, Mario Smarduch wrote:
> > On 01/22/2015 01:34 AM, Paul Bolle wrote:
> >> Mario,
> >>
> >> Your commit c64735554c0a ("KVM: arm: Add initial dirty page locking
> >> support") is included in today's linux-next (ie, next-20150122). I
> >> noticed because a script I use to check linux-next spotted a minor
> >> problem with it.
> >>
> >> This commit added a comment that mentions CONFIG_LOCK_DEP and
> >> CONFIG_LOCK_DETECTOR. It seems CONFIG_LOCKDEP and CONFIG_LOCKUP_DETECTOR
> >> should be used instead. Is a trivial patch to fix these typos queued
> >> somewhere?
> >>
> >> Thanks,
> >>
> >>
> >> Paul Bolle
> >>
> >
> > Hi Paul,
> > thanks for spotting that. No there is no trivial patch
> > queued, didn't notice it until now. Can I submit a follow
> > up trivial patch later?
>
> Yeah, that can definitely wait. I think we have slightly bigger fish to
> fry for now... ;-)
>
> If someone sends us a patch once -rc1 is out, we'll queue it.
>
I'll just fix it up before sending the pull request today.
-Christoffer
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: KVM: CONFIG_LOCK_DEP and CONFIG_LOCK_DETECTOR?
@ 2015-01-23 9:44 ` Christoffer Dall
0 siblings, 0 replies; 9+ messages in thread
From: Christoffer Dall @ 2015-01-23 9:44 UTC (permalink / raw)
To: Marc Zyngier
Cc: Mario Smarduch, Paul Bolle, Valentin Rothberg, Gleb Natapov,
Paolo Bonzini, Russell King, kvm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu, linux-kernel@vger.kernel.org
On Thu, Jan 22, 2015 at 07:18:25PM +0000, Marc Zyngier wrote:
> On 22/01/15 19:13, Mario Smarduch wrote:
> > On 01/22/2015 01:34 AM, Paul Bolle wrote:
> >> Mario,
> >>
> >> Your commit c64735554c0a ("KVM: arm: Add initial dirty page locking
> >> support") is included in today's linux-next (ie, next-20150122). I
> >> noticed because a script I use to check linux-next spotted a minor
> >> problem with it.
> >>
> >> This commit added a comment that mentions CONFIG_LOCK_DEP and
> >> CONFIG_LOCK_DETECTOR. It seems CONFIG_LOCKDEP and CONFIG_LOCKUP_DETECTOR
> >> should be used instead. Is a trivial patch to fix these typos queued
> >> somewhere?
> >>
> >> Thanks,
> >>
> >>
> >> Paul Bolle
> >>
> >
> > Hi Paul,
> > thanks for spotting that. No there is no trivial patch
> > queued, didn't notice it until now. Can I submit a follow
> > up trivial patch later?
>
> Yeah, that can definitely wait. I think we have slightly bigger fish to
> fry for now... ;-)
>
> If someone sends us a patch once -rc1 is out, we'll queue it.
>
I'll just fix it up before sending the pull request today.
-Christoffer
^ permalink raw reply [flat|nested] 9+ messages in thread