From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752359Ab3EJJUv (ORCPT ); Fri, 10 May 2013 05:20:51 -0400 Received: from 173-166-109-252-newengland.hfc.comcastbusiness.net ([173.166.109.252]:58047 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752237Ab3EJJUu (ORCPT ); Fri, 10 May 2013 05:20:50 -0400 Date: Fri, 10 May 2013 11:19:12 +0200 From: Peter Zijlstra To: Sasha Levin Cc: torvalds@linux-foundation.org, mingo@kernel.org, linux-kernel@vger.kernel.org, jamie.iles@oracle.com, penberg@kernel.org, acme@ghostprotocols.net, paulus@samba.org, namhyung@kernel.org, Andrew Morton , Thomas Gleixner Subject: Re: [PATCH v3 8/9] liblockdep: Add the 'lockdep' user-space utility Message-ID: <20130510091912.GD3039@dyad.programming.kicks-ass.net> References: <1368115089-8909-1-git-send-email-sasha.levin@oracle.com> <1368115089-8909-9-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-9-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:08AM -0400, Sasha Levin wrote: > This is a simple wrapper to make using liblockdep on existing > applications much easier. > > After running 'make && make install', it becomes quite simple to > test things with liblockdep. For example, to try it on perf: > > lockdep perf > > No other integration required. > > Signed-off-by: Sasha Levin > Cc: jamie.iles@oracle.com > Cc: penberg@kernel.org > Cc: acme@ghostprotocols.net > Cc: paulus@samba.org > Cc: namhyung@kernel.org > Cc: peterz@infradead.org That's me > Cc: Linus Torvalds > Cc: Andrew Morton > Cc: Peter Zijlstra That too.. > Cc: Thomas Gleixner > Link: http://lkml.kernel.org/r/1360456781-32462-11-git-send-email-sasha.levin@oracle.com > Signed-off-by: Ingo Molnar I was wondering why I kept getting this particular patch twice every time..