Re: KVM: CONFIG_LOCK_DEP and CONFIG_LOCK_DETECTOR?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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...
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux