From: christoffer.dall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: KVM: CONFIG_LOCK_DEP and CONFIG_LOCK_DETECTOR?
Date: Fri, 23 Jan 2015 10:44:31 +0100 [thread overview]
Message-ID: <20150123094431.GI15076@cbox> (raw)
In-Reply-To: <54C14D01.2010506@arm.com>
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
prev parent reply other threads:[~2015-01-23 9:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-22 9:34 KVM: CONFIG_LOCK_DEP and CONFIG_LOCK_DETECTOR? Paul Bolle
2015-01-22 19:13 ` Mario Smarduch
2015-01-22 19:18 ` Marc Zyngier
2015-01-23 9:44 ` Christoffer Dall [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150123094431.GI15076@cbox \
--to=christoffer.dall@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).