Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp2994617ybb; Sun, 22 Mar 2020 12:37:06 -0700 (PDT) X-Google-Smtp-Source: ADFU+vustfYsmMBJH486WaC382YX9WFvBupwwIPRwW1tbuxdf/H066N3FV6U6jw7EGRVe3JwcLIY X-Received: by 2002:a9d:a68:: with SMTP id 95mr14601235otg.87.1584905825931; Sun, 22 Mar 2020 12:37:05 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1584905825; cv=none; d=google.com; s=arc-20160816; b=hwf07OfO4mmTggkaPZEiOBRJLbcA/HAayK/hB/lokl+YmgxpaZLbuH8DVyX0PvhuSj sMEIlcWNPxmiRNpogJUHAMjmcqWkKrYSKjifJgelNxvbwD45u+AgARYzsFncj63gYrV0 ZI4d/zf/ttWORYT0NbBrPF+i4cgVrbscMB87uiaiamK2nQ4ke/6ebVhmP3nLrXTKNCq1 /ENayrfxWCNDs7bp+tJNML1qivhNM4Zumez1XyJ2Hel1UvVBaCMYV2+YuRiFrLmrSsNW kH60dhPvPVkLg1/niMmSDspSBxuBQJO5wIllkFxf+L/baBIOcpU2Pm5BH4LQVgbXiRic Saug== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:message-id:references :in-reply-to:subject:cc:to:from:date:content-transfer-encoding :mime-version:dkim-signature; bh=lxaxXDJrPl2nbBmgQOPbFgqdiD/rS7e2ntsmN/8fsj4=; b=b5rc7aWfSnWeeSPX5X88F3gfoDATgzs+x6sT27JPFXKpHKsBYn8c9AW0R++/6SpCgK 7kYCUn4KbieF8q3AJNcIu0hxBF50PRbljxp1hNedc3nmaX/2bfU9LNYBrfiOxNBVZTOe qHNzTedDLg3UKEnSy1nArSHB1E6/fkQZ01tgwMkSNE+EAG9XpMcu2SIl78S7uAYP1WAU UcUCo4p5hx7fypAmZzJqrC/t47Ngvt8htpugQXUgA9Y2TVqzpQwc00w+jdvmrmR66O0J On8/qTtiSIA2D7LuxoQI33fLLwcmlqUygV50Z4cq91R1Atl+O7X2hSE/ouaFOguYj6aQ cI+Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=kAXEx17a; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id n4si6164688oic.213.2020.03.22.12.36.38; Sun, 22 Mar 2020 12:37:05 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=kAXEx17a; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726783AbgCVTgA (ORCPT + 99 others); Sun, 22 Mar 2020 15:36:00 -0400 Received: from mail.kernel.org ([198.145.29.99]:46734 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726502AbgCVTf7 (ORCPT ); Sun, 22 Mar 2020 15:35:59 -0400 Received: from disco-boy.misterjones.org (disco-boy.misterjones.org [51.254.78.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id CB6172070A; Sun, 22 Mar 2020 19:35:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1584905759; bh=iL1sjTLvw1JVu+N++3CO4C0/tIF4N6blP9U1IKYS5gQ=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=kAXEx17aS3TrizisnrRafSOkN+ibt5U0Y7672k6/Yrcv7ai6MHzcqZgalHr4qyo/W A215K6TVqFPDF3E6GPENUbZiJDMKPTfFhFXiwNllNT5vdOKjOmD9nBjxHQmuWx7aLI wpzmhLnSjrqktPegHm6AwDxvzGfDny/5xovTe7Yk= Received: from disco-boy.misterjones.org ([51.254.78.96] helo=www.loen.fr) by disco-boy.misterjones.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jG6O5-00Eknk-0F; Sun, 22 Mar 2020 19:35:57 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Sun, 22 Mar 2020 19:35:56 +0000 From: Marc Zyngier To: Daniel Baluta Cc: Anson Huang , tglx@linutronix.de, jason@lakedaemon.net, Shawn Guo , Sascha Hauer , Pengutronix Kernel Team , Fabio Estevam , Linux Kernel Mailing List , linux-arm-kernel , dl-linux-imx Subject: Re: [PATCH] irqchip: irq-imx-gpcv2: Remove unnecessary blank lines In-Reply-To: References: <1584421001-2647-1-git-send-email-Anson.Huang@nxp.com> <86mu89zqce.wl-maz@kernel.org> Message-ID: X-Sender: maz@kernel.org User-Agent: Roundcube Webmail/1.3.10 X-SA-Exim-Connect-IP: 51.254.78.96 X-SA-Exim-Rcpt-To: daniel.baluta@gmail.com, Anson.Huang@nxp.com, tglx@linutronix.de, jason@lakedaemon.net, shawnguo@kernel.org, s.hauer@pengutronix.de, kernel@pengutronix.de, festevam@gmail.com, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Linux-imx@nxp.com X-SA-Exim-Mail-From: maz@kernel.org X-SA-Exim-Scanned: No (on disco-boy.misterjones.org); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Daniel, On 2020-03-22 19:08, Daniel Baluta wrote: > On Sat, Mar 21, 2020 at 5:22 PM Marc Zyngier wrote: >> >> On Tue, 17 Mar 2020 04:56:41 +0000, >> Anson Huang wrote: >> > >> > Remove unnecessary blank lines for cleanup. >> > >> > Signed-off-by: Anson Huang >> > --- >> > drivers/irqchip/irq-imx-gpcv2.c | 2 -- >> > 1 file changed, 2 deletions(-) >> > >> > diff --git a/drivers/irqchip/irq-imx-gpcv2.c b/drivers/irqchip/irq-imx-gpcv2.c >> > index 4f74c15..4f11b9b 100644 >> > --- a/drivers/irqchip/irq-imx-gpcv2.c >> > +++ b/drivers/irqchip/irq-imx-gpcv2.c >> > @@ -17,7 +17,6 @@ >> > #define GPC_IMR1_CORE2 0x1c0 >> > #define GPC_IMR1_CORE3 0x1d0 >> > >> > - >> > struct gpcv2_irqchip_data { >> > struct raw_spinlock rlock; >> > void __iomem *gpc_base; >> > @@ -287,6 +286,5 @@ static int __init imx_gpcv2_irqchip_init(struct device_node *node, >> > of_node_clear_flag(node, OF_POPULATED); >> > return 0; >> > } >> > - >> > IRQCHIP_DECLARE(imx_gpcv2_imx7d, "fsl,imx7d-gpc", imx_gpcv2_irqchip_init); >> > IRQCHIP_DECLARE(imx_gpcv2_imx8mq, "fsl,imx8mq-gpc", imx_gpcv2_irqchip_init); >> >> I honestly don't think this deserves a patch. Next time you work on >> this driver, add the cleanups to it. But on its own, it's only churn. > > While you are technically right, it's only churn I think we need this > for code consistency and cleanup. Get real. We really don't. Two blank lines do not lead to a misinterpretation of the code, do not get in the way of normal maintenance, do not lead to *any* practical issue. What's next? Cc stable? > Even if we fix this when we work on the driver we still need > to make the cleanup in a separate patch. Neither. As well as removing blank lines, you could also remove the dead code in this driver. That would be a good cleanup. You could also have a look at what feels like a potential deadlock in the mask/unmask callbacks. That'd be a good thing to do too. Certainly more useful than just dropping two blank lines. M. -- Jazz is not dead. It just smells funny...