Received: by 2002:a05:6a10:6006:0:0:0:0 with SMTP id w6csp992257pxa; Fri, 28 Aug 2020 00:04:39 -0700 (PDT) X-Google-Smtp-Source: ABdhPJw5/8vsBKUqMoOOjakg9E/oZFb7rK+YRQp3dEi7jWI/f6Lm1y5wICu4gdGc84I0Gwp6XGMG X-Received: by 2002:a50:d78e:: with SMTP id w14mr428233edi.229.1598598278800; Fri, 28 Aug 2020 00:04:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1598598278; cv=none; d=google.com; s=arc-20160816; b=zDq0OIDuECU9fOHHWF7bj/QGSmnNJ1CFw2SP8ITWnn20yk6u1ifV7/AX19JWXEzqgY oDhz+H62BvtxXFgWxcHRuTLiAwl8yLpIesFQfL1ZOdu25GfFc095ZOo+PtaA3b5OozAh pqETJOWM61T6DeN/Z3k/4ijHZ3ppT9tG9xh41lEeyEs9wtB8y72ZImAmom9/nV5kyyzi VM9BPDdfNh8RscJsObENQ98kNqCgpO3fnPFLRN9IgDCLkBi9nhXqgBFi0JTM8zGBik0x KcUlXn1csEUzSrgwdwT3+TJJOQwdfYzbLdyjRzfdp0RNFGMS/OHueuXSA2qYrxwo2Lh2 Qhww== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=woAA94wxhse9phtGHIK8nX9vSd6IUbHDkjttjAy7cAc=; b=WPkISQk4fu/6O1u9GibXNIbJfwWo6DG06NgFxB+6sqg+bf74UZLYy5Nfvnu9MDsAhN OTT2PEyLnyzk/69Tzbnf+v4aXvkQ9pN8N6QFgsnrpbkJhwPMV75dNXPDmMiuMJ0YHKdS hBDLFKo+nLIbz1xBAfHHC12QM4qMsfqO1DamISr60da9xuAX+PzyLucqldwW+l1iMSXy kaJiEWWni86tWIBJYkfPxkr1rnuSIDLeOnX2LjbKGZKNMBgotSfueFR5683fI+M9z6MF y0846uj84/7w6J1rlBFGJhz3v8/yHzRKnevujrWil+F8NCFaMklH/yw4GNcTWQPd3xGM L0Xw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=sx7QHngC; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id c3si81029ejm.314.2020.08.28.00.04.15; Fri, 28 Aug 2020 00:04:38 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=sx7QHngC; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727968AbgH1HDU (ORCPT + 99 others); Fri, 28 Aug 2020 03:03:20 -0400 Received: from mail.kernel.org ([198.145.29.99]:57730 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725858AbgH1HDT (ORCPT ); Fri, 28 Aug 2020 03:03:19 -0400 Received: from mail-ej1-f41.google.com (mail-ej1-f41.google.com [209.85.218.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id A10D8214DB; Fri, 28 Aug 2020 07:03:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1598598198; bh=4faSGkxwde2dUgjoJLxEPngM/PNDuiR7AsduftolHIs=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=sx7QHngCjfwrj5EpTWFj8h72BUzgxBMBKywR+k595Wk3fByAORr3jVBGDZLwGksw0 PYNKYbUpEnueECWfETWbOSoHpehiGjPGGdGrQ1xkURBaro59NTzuZqovK+ftZZdWmw BIoHuIn6C7rK8aWGwpap/DKCec5A9wvC81kDbajc= Received: by mail-ej1-f41.google.com with SMTP id d11so108999ejt.13; Fri, 28 Aug 2020 00:03:18 -0700 (PDT) X-Gm-Message-State: AOAM530xspcHh02fOCnYcpu+pEaZfgTuO3YftEMnW6YqSQJLP8coGynN FfZwslcwId8hf8v6/WuJ3pMAsgVOo+ma1icz9NA= X-Received: by 2002:a17:906:3e0a:: with SMTP id k10mr409528eji.148.1598598197045; Fri, 28 Aug 2020 00:03:17 -0700 (PDT) MIME-Version: 1.0 References: <20200827192642.1725-1-krzk@kernel.org> <20200827192642.1725-9-krzk@kernel.org> <20200828062443.GA17343@pi3> <3a5cb59b-454e-2c3f-9f31-43147e843c66@axentia.se> In-Reply-To: <3a5cb59b-454e-2c3f-9f31-43147e843c66@axentia.se> From: Krzysztof Kozlowski Date: Fri, 28 Aug 2020 09:03:06 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v2 09/18] iio: afe: iio-rescale: Simplify with dev_err_probe() To: Peter Rosin Cc: Jonathan Cameron , Hartmut Knaack , Lars-Peter Clausen , Peter Meerwald-Stadler , Kukjin Kim , Michael Hennerich , Kevin Hilman , Neil Armstrong , Jerome Brunet , Martin Blumenstingl , Marek Vasut , Maxime Coquelin , Alexandre Torgue , Beniamin Bia , Tomasz Duszynski , Linus Walleij , Andy Shevchenko , linux-iio@vger.kernel.org, "linux-kernel@vger.kernel.org" , linux-arm-kernel@lists.infradead.org, "linux-samsung-soc@vger.kernel.org" , linux-amlogic@lists.infradead.org, linux-stm32@st-md-mailman.stormreply.com Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 28 Aug 2020 at 08:58, Peter Rosin wrote: > >> I'm not a huge fan of adding *one* odd line breaking the 80 column > >> recommendation to any file. I like to be able to fit multiple > >> windows side by side in a meaningful way. Also, I don't like having > >> a shitload of emptiness on my screen, which is what happens when some > >> lines are longer and you want to see it all. I strongly believe that > >> the 80 column rule/recommendation is still as valid as it ever was. > >> It's just hard to read longish lines; there's a reason newspapers > >> columns are quite narrow... > >> > >> Same comment for the envelope-detector (3/18). > >> > >> You will probably never look at these files again, but *I* might have > >> to revisit them for one reason or another, and these long lines will > >> annoy me when that happens. > > > > Initially I posted it with 80-characters wrap. Then I received a comment > > - better to stick to the new 100, as checkpatch accepts it. > > > > Now you write, better to go back to 80. > > > > Maybe then someone else will write to me, better to go to 100. > > > > And another person will reply, no, coding style still mentions 80, so > > keep it at 80. > > > > Sure guys, please first decide which one you prefer, then I will wrap it > > accordingly. :) > > > > Otherwise I will just jump from one to another depending on one person's > > personal preference. > > > > If there is no consensus among discussing people, I find this 100 line > > more readable, already got review, checkpatch accepts it so if subsystem > > maintainer likes it, I prefer to leave it like this. > > I'm not impressed by that argument. For the files I have mentioned, it > does not matter very much to me if you and some random person think that > 100 columns might *slightly* improve readability. > > Quoting coding-style > > Statements longer than 80 columns should be broken into sensible chunks, > unless exceeding 80 columns significantly increases readability and does > not hide information. > > Notice that word? *significantly* Notice also checkpatch change... First of all, I don't have a preference over wrapping here. As I said, I sent v1 with 80 and got a response to change it to 100. You want me basically to bounce from A to B to A to B. > Why do I even have to speak up about this? WTF? Because we all share here our ideas... > For the patches that touch files that I originally wrote [1], my > preference should be clear by now. I understood your preference. There is nothing unclear here. Other person had different preference. I told you my arguments that it is not reasonable to jump A->B->A->B just because each person has a different view. At the end it's the subsystem maintainer's decision as he wants to keep his subsystem clean. Best regards, Krzysztof