[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <54C14D01.2010506@arm.com>
Date: Thu, 22 Jan 2015 19:18:25 +0000
From: Marc Zyngier <marc.zyngier@....com>
To: Mario Smarduch <m.smarduch@...sung.com>,
Paul Bolle <pebolle@...cali.nl>
CC: Valentin Rothberg <valentinrothberg@...il.com>,
Christoffer Dall <christoffer.dall@...aro.org>,
Gleb Natapov <gleb@...nel.org>,
Paolo Bonzini <pbonzini@...hat.com>,
Russell King <linux@....linux.org.uk>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"kvmarm@...ts.cs.columbia.edu" <kvmarm@...ts.cs.columbia.edu>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: KVM: CONFIG_LOCK_DEP and CONFIG_LOCK_DETECTOR?
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 linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists