From: Christoph Lameter <cl@linux.com>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>,
Johannes Weiner <hannes@cmpxchg.org>,
kbuild-all@01.org
Subject: Re: [mmotm:master 463/499] mm/mprotect.c:46:14: sparse: context imbalance in 'lock_pte_protection' - different lock contexts for basic block
Date: Mon, 24 Mar 2014 16:00:32 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.2.10.1403241559390.29809@nuc> (raw)
In-Reply-To: <532e4cc1.umGiNE2YJiL9Z2iq%fengguang.wu@intel.com>
On Sun, 23 Mar 2014, kbuild test robot wrote:
> >> mm/mprotect.c:46:14: sparse: context imbalance in 'lock_pte_protection' - different lock contexts for basic block
> >> arch/x86/include/asm/paravirt.h:699:9: sparse: context imbalance in 'change_pte_range' - unexpected unlock
> --
> >> fs/ntfs/super.c:3100:1: sparse: directive in argument list
> >> fs/ntfs/super.c:3102:1: sparse: directive in argument list
> >> fs/ntfs/super.c:3104:1: sparse: directive in argument list
> >> fs/ntfs/super.c:3105:1: sparse: directive in argument list
> >> fs/ntfs/super.c:3107:1: sparse: directive in argument list
> >> fs/ntfs/super.c:3108:1: sparse: directive in argument list
> >> fs/ntfs/super.c:3110:1: sparse: directive in argument list
Looked through these and I am a bit puzzled how they related to raw cpu
ops patch.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2014-03-24 21:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-23 2:53 kbuild test robot
2014-03-24 21:00 ` Christoph Lameter [this message]
2014-03-25 2:28 ` Fengguang Wu
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=alpine.DEB.2.10.1403241559390.29809@nuc \
--to=cl@linux.com \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=peterz@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