Received: by 10.223.185.116 with SMTP id b49csp427786wrg; Fri, 23 Feb 2018 00:43:34 -0800 (PST) X-Google-Smtp-Source: AH8x224+BOU80LXnjfH6jkC5XF1M3TdMOscJGdzFOTuNt9GweT7m21Z5jqdYNZKPNeIWFzs2wdya X-Received: by 2002:a17:902:a985:: with SMTP id bh5-v6mr1007825plb.230.1519375413999; Fri, 23 Feb 2018 00:43:33 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519375413; cv=none; d=google.com; s=arc-20160816; b=fXFuTTNbgl62O9yvtUftjEryhpWEMnN5ODgrX34jvR5ajij7orAcRkF4s+iNNYHlT9 4g2UjDkXeVt5q3CLN1YFzpXdAd74Gce42Qv4Vh3C9NsCz2WRlmZKxVS9j/nFUtjx1lP0 qJmrUCB9WoS0wBx/X0r+QYAq7IqCROdK4l2xHpMwe/mVb7ldBih0xl5UnUaDIOaeR2ao 0T8nPiU3yRwqzXInWnQnJKVVyZPY9X6mGZPwqSUwcqoRjlh3uh24hQjsBhszJ/sfd0Y4 VrZcxHueGY/ZBNlp3JxdiVGqBa00PkmEOCKMgeMMuDseOFYtetoWluXfaRhiBBsDeCwl 5CqA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date :arc-authentication-results; bh=7B4WIOXWDP6yky6rTh89kO6/aPvgav7Np4Jv3HiVTmU=; b=hf4xZbi+tUi5Dvz79lN1ICmm3mh0Prf3lpQniOnVf98KceA5iKsDKltULnU+osc1d/ NwHo7+O+xHh6OT1oCttTvpJ4oYu7hSXshYRj6zm9eIOX3kpV5B9ZiAkdQJrXs36T93hq fdxo+QMQ4cTi6pBGGNgczi3eqSiksXYs099J+DCe9I9EDVR0Nz7yE/BCSfw+i8A+9T6h shg6WZTK14prER8lD1tEYWKxqw+9d1fR6XPIt6PVFtdwk84c2AlLaDr+zBZfCYGg3axx 4VEjOQ0n0keTxcvw9+ucIoV3QBsFR1S5NdAUbBx47rs0RUlUNExMaw8dpGWcu8wOf5rj H6lA== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v187si1472733pfv.173.2018.02.23.00.43.19; Fri, 23 Feb 2018 00:43:33 -0800 (PST) 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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751440AbeBWImj (ORCPT + 99 others); Fri, 23 Feb 2018 03:42:39 -0500 Received: from Galois.linutronix.de ([146.0.238.70]:40532 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750879AbeBWImh (ORCPT ); Fri, 23 Feb 2018 03:42:37 -0500 Received: from [37.80.204.220] by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1ep8se-0007Zt-7K; Fri, 23 Feb 2018 09:39:00 +0100 Date: Fri, 23 Feb 2018 09:42:38 +0100 (CET) From: Thomas Gleixner To: Radoslaw Pietrzyk cc: Jason Cooper , Marc Zyngier , Maxime Coquelin , Alexandre Torgue , Linus Walleij , Benjamin Gaignard , Philipp Zabel , linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-gpio@vger.kernel.org, Ludovic BARRE Subject: Re: [PATCH v2 1/2] irqchip: stm32: Optimizes and cleans up stm32-exti irq_domain In-Reply-To: <6491f248c6748f21a2acf310e186d2be4f9b4e4c.1519374248.git.radoslaw.pietrzyk@gmail.com> Message-ID: References: <6491f248c6748f21a2acf310e186d2be4f9b4e4c.1519374248.git.radoslaw.pietrzyk@gmail.com> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Radoslaw, On Fri, 23 Feb 2018, Radoslaw Pietrzyk wrote: > - discards setting handle_simple_irq handler for hierarchy interrupts > - removes acking in chained irq handler as this is done by > irq_chip itself inside handle_edge_irq > - removes unneeded irq_domain_ops.xlate callback if that's all functionally correct, then this is a nice cleanup. Though from the above changelog its hard to tell because it merily tells WHAT the patch does, but not WHY. The WHY is the important information for a reviewer who is not familiar with the particular piece of code/hardware. Can you please amend the changelog with proper explanations why a particular piece of code is not needed or has to be changed to something else? Thanks, tglx