From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933586Ab3CZNJ4 (ORCPT ); Tue, 26 Mar 2013 09:09:56 -0400 Received: from hydra.sisk.pl ([212.160.235.94]:42959 "EHLO hydra.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932679Ab3CZNJy (ORCPT ); Tue, 26 Mar 2013 09:09:54 -0400 From: "Rafael J. Wysocki" To: Tang Chen Cc: lenb@kernel.org, robert.moore@intel.com, lv.zheng@intel.com, ming.m.lin@intel.com, mpm@selenic.com, herbert@gondor.hengli.com.au, rob@landley.net, linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org Subject: Re: [RESEND PATCH 1/6] acpi: Remove the leading space of "unlock" label in acpi_memory_device_notify(). Date: Tue, 26 Mar 2013 14:17:17 +0100 Message-ID: <1843378.VZBEQ0WNNo@vostro.rjw.lan> User-Agent: KMail/4.9.5 (Linux/3.9.0-rc4+; KDE/4.9.5; x86_64; ; ) In-Reply-To: <1362558611-32255-2-git-send-email-tangchen@cn.fujitsu.com> References: <1362558611-32255-1-git-send-email-tangchen@cn.fujitsu.com> <1362558611-32255-2-git-send-email-tangchen@cn.fujitsu.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wednesday, March 06, 2013 04:30:06 PM Tang Chen wrote: > There is a leading space in front of "unlock" label in acpi_memory_device_notify(). Remove it. > > Signed-off-by: Tang Chen > --- > drivers/acpi/acpi_memhotplug.c | 2 +- > 1 files changed, 1 insertions(+), 1 deletions(-) > > diff --git a/drivers/acpi/acpi_memhotplug.c b/drivers/acpi/acpi_memhotplug.c > index da1f82b..8a10c23 100644 > --- a/drivers/acpi/acpi_memhotplug.c > +++ b/drivers/acpi/acpi_memhotplug.c > @@ -369,7 +369,7 @@ static void acpi_memory_device_notify(acpi_handle handle, u32 event, void *data) > kfree(ej_event); > } > > - unlock: > +unlock: > acpi_scan_lock_release(); > if (ACPI_SUCCESS(status)) > return; The leading space is actually in agreement with the kernel coding style (and there's a reason why it's there). Thanks, Rafael -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center.