Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp7058000imm; Tue, 24 Jul 2018 07:46:18 -0700 (PDT) X-Google-Smtp-Source: AAOMgpevnXKwq/9Odfx7Bi041sgNsjMWZG9bOA+lw08zHUSo9Cel44DHxuYmsTZM2lWXHprxIVSR X-Received: by 2002:a17:902:7894:: with SMTP id q20-v6mr17623457pll.3.1532443578087; Tue, 24 Jul 2018 07:46:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1532443578; cv=none; d=google.com; s=arc-20160816; b=U+w9I7mMWzjACTAnbkG/XyQc8KgGa7/M8n0ULNYruPjXnG6GgmETyqYwW4KdF05oBS RYUhT5/Mu/XZ1HpS2jDBKlKkXHLbLyQjT2wovASJEk22nEiqhiC168a3EVN6ybe4INoK sJ96fPh5MXenLOyKgBo4j9KiBoMu/isH+fCgpYydlmfgiOSsMUM3J/4D4VQrJoaMoCS3 E1OWpmNLdFcCob5h7RMqF4cRmH3JiRrE7teNDyNq9nytFdH2OBhb3Dhmi3i/4FU8HBlP BbHhG81ooXFhPvMfeTaYuANzfcFRDSyfEZkrBrmgn0OB4F7kNTNpYtXnRc2Tue2KSlJo LKjA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :organization:references:in-reply-to:message-id:subject:cc:to:from :date:arc-authentication-results; bh=mj9fuGNMnoWen6/x8q5ZFF1Jm4l72dNozqsThWRlovY=; b=aNpd6I1BPJvyh88PosljWu1Njo9aPfEYN+JYDIv5LA9kxLVWkgva0ORbzbRYH1+hxt DguFdQCwlNaANwxkVdW79R6eI9rdb5lIqBNagMjDTePLpRiZjRQHLlRjRT+RBxZPv5vZ Q3KSokYNkYxJNJDAckjYImENM1mFGxD4xStqVL7Z0h6kK+qwCwkxGSFJKrCm04zDGYOQ cJEeA7+CUTPmYQvlG1z2r8o+NeBbT2ef4LqfK7IXg/JvYmwwmmWmnk1nzp8Ky/UD65N6 dVfiEaqz3Nq1bUOTSy010rMnfqriYxHtGRKzbEof0KlS35iwythBUttgLk1sq2z2N8cf nrBg== 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 d124-v6si10936563pfg.366.2018.07.24.07.46.02; Tue, 24 Jul 2018 07:46:18 -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; 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 S2388614AbeGXPvJ (ORCPT + 99 others); Tue, 24 Jul 2018 11:51:09 -0400 Received: from mail.bootlin.com ([62.4.15.54]:36290 "EHLO mail.bootlin.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2388495AbeGXPvI (ORCPT ); Tue, 24 Jul 2018 11:51:08 -0400 Received: by mail.bootlin.com (Postfix, from userid 110) id 3D434207AD; Tue, 24 Jul 2018 16:44:18 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on mail.bootlin.com X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,SHORTCIRCUIT, URIBL_BLOCKED shortcircuit=ham autolearn=disabled version=3.4.0 Received: from windsurf (176.199.29.109.rev.sfr.net [109.29.199.176]) by mail.bootlin.com (Postfix) with ESMTPSA id C8062206A6; Tue, 24 Jul 2018 16:44:07 +0200 (CEST) Date: Tue, 24 Jul 2018 16:44:07 +0200 From: Thomas Petazzoni To: Sam Ravnborg Cc: "David S . Miller" , sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org, Marc Zyngier , Hanna Hawa Subject: Re: [PATCH 1/2] sparc: move MSI related definitions to where they are used Message-ID: <20180724164407.4fa57d1f@windsurf> In-Reply-To: <20180724143736.GA22088@ravnborg.org> References: <20180724115305.11289-1-thomas.petazzoni@bootlin.com> <20180724143736.GA22088@ravnborg.org> Organization: Bootlin (formerly Free Electrons) X-Mailer: Claws Mail 3.15.1-dirty (GTK+ 2.24.32; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, Thanks for the review. On Tue, 24 Jul 2018 16:37:36 +0200, Sam Ravnborg wrote: > One nitpick below. > But other than that this is a nice cleanup: > Acked-by: Sam Ravnborg > > +/* > > + * Locations of MSI Registers. > > + */ > > The SPARC way to format comments follows netdev style. > So put it all in one line and everyone are happy: Well, the code is being moved from arch/sparc to arch/sparc, so apparently, it was already non-compliant to this specific coding style rule. Should the comments be made compliant as part of the same commit, or a separate one ? Thomas -- Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons) Embedded Linux and Kernel engineering https://bootlin.com