Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933146Ab2JSWO3 (ORCPT ); Fri, 19 Oct 2012 18:14:29 -0400 Received: from mail-wg0-f44.google.com ([74.125.82.44]:51471 "EHLO mail-wg0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933002Ab2JSWOY (ORCPT ); Fri, 19 Oct 2012 18:14:24 -0400 MIME-Version: 1.0 In-Reply-To: <1350570446.22036@cat.he.net> References: <1350570446.22036@cat.he.net> Date: Fri, 19 Oct 2012 15:14:22 -0700 X-Google-Sender-Auth: aqw5822qzciDh2aW5tJO8KTwEH8 Message-ID: Subject: Re: [PATCH] Documentation/sparse.txt: document context annotations for lock checking From: Christopher Li To: Ed Cashin Cc: akpm@linux-foundation.org, josh@joshtriplett.org, rob@landley.net, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-sparse@vger.kernel.org, sam@ravnborg.org, ak@linux.intel.com Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 690 Lines: 17 On Thu, Oct 18, 2012 at 7:27 AM, Ed Cashin wrote: > The context feature of sparse is used with the Linux kernel > sources to check for imbalanced uses of locks. Document the > annotations defined in include/linux/compiler.h that tell sparse > what to expect when a lock is held on function entry, exit, or > both. > > Signed-off-by: Ed Cashin Signed-off-by: Christopher Li Chris -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/