Received: by 2002:a05:6a10:f3d0:0:0:0:0 with SMTP id a16csp4916954pxv; Tue, 6 Jul 2021 12:21:10 -0700 (PDT) X-Google-Smtp-Source: ABdhPJy61GM6mfStQvQQt2n/UsFRgGPFa2IQi+Ho7B/ZQ9vC258MyylTpjpLdu1sJVf0Egez/W0c X-Received: by 2002:a05:6402:d06:: with SMTP id eb6mr24557105edb.337.1625599269752; Tue, 06 Jul 2021 12:21:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1625599269; cv=none; d=google.com; s=arc-20160816; b=Zb7+nLIpb7u7lN+d+VmLVf6gjvOndAdMENv5HDlD0R0C9IA/V9s898c2kPiV++0Aev nXT4way7gvoHmLYnOiaAJytVV3C8axFxH/DMzs0j1FumOZ9846YSLo7urTi5U5sveJxk nzfWx97M89Hc9shXpjbg7RuhLm95g3HLY+Blqet+hA/VW1BHCcFs/ANRpiL0lpFGBaAY KPBjKkJPyaBiC0MXNAvpbSBWiW1cIx8FViGqZaW5K6ztifPu/k0VtXTBW/k9DgFxaMb5 6ycxvo4OZs6HMo9H/DfoRdrM4fIQMNM116brNkimRb49hyMHIkodBGzy4CvddbxB0JkH fo7Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=ioRwsBKr1SkP1S5lmj5HNKHA3qFOhHRaqEb71qYkw9o=; b=g5C9NuP2fy+OPGxKgHwlKVgMbgszhqk0zEauJyu7coh6Y9EREzNWKH9msCQekHpdv2 GNAJByTlCaWnMXQ6PPZdryxTVPR1tkUBj11daA+6NFM+vXcCdUcLiDp3yUa6MSyrY6qr r0ZfPm7qNZjeU9mM1Zc0jESh5LVW+5PorGBC/t51yFGUfv/MJzmbjKCd+zWZiGbsMfpt LS2En4fUDni4tjoxwlk6d542z6tZy97aV+L9iIrWjwlYJGJQ9dMRb2Bcj3yHOQj7ql++ 99m0E7etEhx+7j/5ylz7NsqNS2ggl9m3uF0FJE425ZjOG+GIrdr0MyfTvipc9p6oNTi1 NOiQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id v9si14803006ejc.307.2021.07.06.12.20.39; Tue, 06 Jul 2021 12:21:09 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231716AbhGFTXK (ORCPT + 99 others); Tue, 6 Jul 2021 15:23:10 -0400 Received: from outgoing-auth-1.mit.edu ([18.9.28.11]:45102 "EHLO outgoing.mit.edu" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S231773AbhGFTXI (ORCPT ); Tue, 6 Jul 2021 15:23:08 -0400 Received: from cwcc.thunk.org (pool-72-74-133-215.bstnma.fios.verizon.net [72.74.133.215]) (authenticated bits=0) (User authenticated as tytso@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 166JKL7Z013101 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 6 Jul 2021 15:20:22 -0400 Received: by cwcc.thunk.org (Postfix, from userid 15806) id 6EFB115C3CC6; Tue, 6 Jul 2021 15:20:21 -0400 (EDT) Date: Tue, 6 Jul 2021 15:20:21 -0400 From: "Theodore Ts'o" To: Jan Gruber Cc: adilger.kernel@dilger.ca, trivial@kernel.org, linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] ext4: Fix comments and spaces to follow coding style Message-ID: References: <20210706183900.310975-1-j4n6ru@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210706183900.310975-1-j4n6ru@gmail.com> Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org On Tue, Jul 06, 2021 at 08:39:00PM +0200, Jan Gruber wrote: > This commit addresses two whitespace issues as well as > instances of the following coding style issue regarding > block comments, which were identified by checkpatch.pl: > > "WARNING: Block comments use a trailing */ on a separate line" > > The changes aim at making the code more pleasant to read > and to eliminate warnings > > Signed-off-by: Jan Gruber Please don't send "checkpatch.pl --file" patches for the ext4 file system; if you must, please focus on files in the drivers directory, where they are more welcome. If developers are making changes to a file, fixing some checkpatch.pl whines is fine, but white-sapace only changes just obfuscates "git blame" code archology, and so the costs far outwieghs the costs. "Fix" is also not the right verb to use. For more information please see [1]. [1] https://gist.github.com/17twenty/8154928 If you are looking for subtantive ways of contributing to the ext4 file system, feel free to look at various syzbot warnings[2] and try to figure out what is going on there. [2] https://syzkaller.appspot.com/upstream (In some cases, the syzbot complaint has already been fixed, and it's just a matter of letting syzbot knoww that it has since been fixed by a particular commit. See [3] for more details.) [3] https://github.com/google/syzkaller/blob/master/docs/syzbot.md Cheers, - Ted