Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp7068802imm; Tue, 24 Jul 2018 07:57:14 -0700 (PDT) X-Google-Smtp-Source: AAOMgpcfJQthG0DpSd+NPmUZd8cJzkfk0kY94DsBbcybVOBE5+F4qJdgWAGKD2aagn8rWUu1Njr+ X-Received: by 2002:a65:550d:: with SMTP id f13-v6mr17021409pgr.340.1532444234035; Tue, 24 Jul 2018 07:57:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1532444234; cv=none; d=google.com; s=arc-20160816; b=SK8CbltxUWgPwu7zvvpTNf/tm7xtPP/g2n1I4/09j8jGkXOdDhWXJ9qK3DpAyE58PD 1l79Y5+YCC5ddOy8IVLvWCVAnMrelFolslzhCQxkOEUaC7tDKBqh8nb0JGBk7MGSVr0o s4hY5kfp2rYbu31leRYEwtQ5lDVRn9227dutHljr0cXsBD9rW0dbR3u+wC2kiPO30in1 zBiycONV7UBdqgMIXLfjLVgX9q5KFPI4J5GSH64tvMMQfliOurr4LLCdlokV6fdsbioe pKABU4gBC9XxlJSQWgAphG4EPJbWtkpw23hyn2i4zodhXNkV4/eu0IsgvCs6SzHc51/u bDcA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=RVCAWab1EH7K7cpDG1y6w9xW6w45aUdB71SQ3teMUKA=; b=C8e5MjUqY2t3BiFZdQ2lBt1FemLpZxKCDGUjYOApSVBBSfpxLq8fAGkTWUx3/SzXNG LDvUE68Y8lckM6nsu9gZHvt/3Vz/Ab72gRIGbIDx+enhzzKCDeeJ9hW0n/Dw6lfU1kxe +aySmenVPLWdE7DeUJgkei9bz3w00GnuVpfLUOxEZgmgRUkdfxs8crDVdDbG6zyKXC7J Gaul7tprrHiCUSRyvWEpzouwyi87NX7i/RKa2x0UmyM6/xLcQQgT+g7lwFAcb1a8Cf8W +a5U+TGlWIRd5CaM1n3ZdNTsSztWqlHm6hZL6HU2G1ZdCSXfepcJgunejnM6nQhVN36L lc7g== 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 73-v6si11031787pgh.343.2018.07.24.07.56.59; Tue, 24 Jul 2018 07:57:14 -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 S2388675AbeGXQCW (ORCPT + 99 others); Tue, 24 Jul 2018 12:02:22 -0400 Received: from asavdk3.altibox.net ([109.247.116.14]:39512 "EHLO asavdk3.altibox.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2388522AbeGXQCV (ORCPT ); Tue, 24 Jul 2018 12:02:21 -0400 Received: from ravnborg.org (unknown [158.248.196.126]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by asavdk3.altibox.net (Postfix) with ESMTPS id 7EBED20023; Tue, 24 Jul 2018 16:55:27 +0200 (CEST) Date: Tue, 24 Jul 2018 16:55:25 +0200 From: Sam Ravnborg To: Thomas Petazzoni 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: <20180724145525.GA14300@ravnborg.org> References: <20180724115305.11289-1-thomas.petazzoni@bootlin.com> <20180724143736.GA22088@ravnborg.org> <20180724164407.4fa57d1f@windsurf> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180724164407.4fa57d1f@windsurf> User-Agent: Mutt/1.5.21 (2010-09-15) X-CMAE-Score: 0 X-CMAE-Analysis: v=2.3 cv=dqr19Wo4 c=1 sm=1 tr=0 a=ddpE2eP9Sid01c7MzoqXPA==:117 a=ddpE2eP9Sid01c7MzoqXPA==:17 a=kj9zAlcOel0A:10 a=KWHQTMtYkH6ttdi61AoA:9 a=CjuIK1q_8ugA:10 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Thomas. > > > > 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 ? Same commit, no reason to slit this in two. So post a v2, then everyone should be happy. I also looked at the second patch which looked obviously correct. Feel free to add my Ack on both. Sam