[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210218083230.GA17913@lst.de>
Date: Thu, 18 Feb 2021 09:32:30 +0100
From: Christoph Hellwig <hch@....de>
To: Ruan Shiyang <ruansy.fnst@...fujitsu.com>
Cc: Christoph Hellwig <hch@....de>, linux-kernel@...r.kernel.org,
linux-xfs@...r.kernel.org, linux-nvdimm@...ts.01.org,
linux-mm@...ck.org, linux-fsdevel@...r.kernel.org,
dm-devel@...hat.com, darrick.wong@...cle.com,
dan.j.williams@...el.com, david@...morbit.com, agk@...hat.com,
snitzer@...hat.com, rgoldwyn@...e.de, qi.fuli@...itsu.com,
y-goto@...itsu.com
Subject: Re: [PATCH v3 05/11] mm, fsdax: Refactor memory-failure handler
for dax mapping
On Wed, Feb 17, 2021 at 10:56:11AM +0800, Ruan Shiyang wrote:
> I'd like to confirm one thing... I have checked all of this patchset by
> checkpatch.pl and it did not report the overly long line warning. So, I
> should still obey the rule of 80 chars one line?
checkpatch.pl is completely broken, I would not rely on it.
Here is the quote from the coding style document:
"The preferred limit on the length of a single line is 80 columns.
Statements longer than 80 columns should be broken into sensible chunks,
unless exceeding 80 columns significantly increases readability and does
not hide information."
Powered by blists - more mailing lists