All of lore.kernel.org
 help / color / mirror / Atom feed
From: pebolle@tiscali.nl (Paul Bolle)
To: linux-arm-kernel@lists.infradead.org
Subject: KVM: CONFIG_LOCK_DEP and CONFIG_LOCK_DETECTOR?
Date: Thu, 22 Jan 2015 10:34:05 +0100	[thread overview]
Message-ID: <1421919245.13638.50.camel@x220> (raw)

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

WARNING: multiple messages have this Message-ID (diff)
From: Paul Bolle <pebolle@tiscali.nl>
To: Mario Smarduch <m.smarduch@samsung.com>
Cc: Valentin Rothberg <valentinrothberg@gmail.com>,
	Christoffer Dall <christoffer.dall@linaro.org>,
	Gleb Natapov <gleb@kernel.org>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Marc Zyngier <marc.zyngier@arm.com>,
	Russell King <linux@arm.linux.org.uk>,
	kvm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	kvmarm@lists.cs.columbia.edu, linux-kernel@vger.kernel.org
Subject: KVM: CONFIG_LOCK_DEP and CONFIG_LOCK_DETECTOR?
Date: Thu, 22 Jan 2015 10:34:05 +0100	[thread overview]
Message-ID: <1421919245.13638.50.camel@x220> (raw)

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


             reply	other threads:[~2015-01-22  9:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-22  9:34 Paul Bolle [this message]
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:13   ` Mario Smarduch
2015-01-22 19:18   ` Marc Zyngier
2015-01-22 19:18     ` Marc Zyngier
2015-01-22 19:18     ` Marc Zyngier
2015-01-23  9:44     ` Christoffer Dall
2015-01-23  9:44       ` Christoffer Dall

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=1421919245.13638.50.camel@x220 \
    --to=pebolle@tiscali.nl \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.