From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752195Ab3EJJTy (ORCPT ); Fri, 10 May 2013 05:19:54 -0400 Received: from 173-166-109-252-newengland.hfc.comcastbusiness.net ([173.166.109.252]:58039 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751745Ab3EJJTx (ORCPT ); Fri, 10 May 2013 05:19:53 -0400 Date: Fri, 10 May 2013 11:18:16 +0200 From: Peter Zijlstra To: Sasha Levin Cc: torvalds@linux-foundation.org, mingo@kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v3 2/9] liblockdep: Wrap kernel/lockdep.c to allow usage from userspace Message-ID: <20130510091816.GC3039@dyad.programming.kicks-ass.net> References: <1368115089-8909-1-git-send-email-sasha.levin@oracle.com> <1368115089-8909-3-git-send-email-sasha.levin@oracle.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1368115089-8909-3-git-send-email-sasha.levin@oracle.com> User-Agent: Mutt/1.5.21 (2012-12-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, May 09, 2013 at 11:58:02AM -0400, Sasha Levin wrote: > kernel/lockdep.c deals with validating locking scenarios for > various architectures supported by the kernel. There isn't > anything kernel specific going on in lockdep, and when we > compare userspace to other architectures that don't have to deal > with irqs such as s390, they become all too similar. > > We wrap kernel/lockdep.c and include/linux/lockdep.h with > several headers which allow us to build and use lockdep from > userspace. We don't touch the kernel code itself which means > that any work done on lockdep in the kernel will automatically > benefit userspace lockdep as well! > > Signed-off-by: Sasha Levin > --- OK, this patch is a complete fail with anything not git. Please fix it so I can use quilt.