From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965310Ab2B1LZS (ORCPT ); Tue, 28 Feb 2012 06:25:18 -0500 Received: from mga03.intel.com ([143.182.124.21]:10684 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965214Ab2B1LZQ (ORCPT ); Tue, 28 Feb 2012 06:25:16 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.71,315,1320652800"; d="scan'208";a="112131203" Date: Tue, 28 Feb 2012 03:25:14 -0800 From: Andi Kleen To: Ingo Molnar Cc: Andrew Morton , Rusty Russell , Nick Piggin , linux-kernel , Alexander Viro , "Srivatsa S. Bhat" , linux-fsdevel@vger.kernel.org Subject: Re: [PATCH] cpumask: fix lg_lock/br_lock. Message-ID: <20120228112514.GD11324@alboin.amr.corp.intel.com> References: <87ehtf3lqh.fsf@rustcorp.com.au> <20120227155338.7b5110cd.akpm@linux-foundation.org> <20120228084359.GJ21106@elte.hu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120228084359.GJ21106@elte.hu> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org As far as I can tell from skimming that lengthy rant it's only about some white space. So the patch must be perfect in substance! -Andi