From: Aleksa Savic <savicaleksa83@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: savicaleksa83@gmail.com, linux-hwmon@vger.kernel.org,
Jack Doan <me@jackdoan.com>, Jean Delvare <jdelvare@suse.com>,
Leonard Anderweit <leonard.anderweit@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hwmon: (aquacomputer_d5next) Fix alignment of function call params
Date: Wed, 12 Apr 2023 07:18:07 +0200 [thread overview]
Message-ID: <9d8194bc-34d0-bbe9-825b-2b7635056a10@gmail.com> (raw)
In-Reply-To: <07419415-3087-48e6-955a-b5024d943e07@roeck-us.net>
On 2023-04-11 22:19:21 GMT+02:00, Guenter Roeck wrote:
> On Tue, Apr 11, 2023 at 08:26:32PM +0200, Aleksa Savic wrote:
>> On 2023-04-10 18:53:08 GMT+02:00, Guenter Roeck wrote:
>>>
>>> I am not sure I understand how this would improve readability.
>>> It seems to accomplish the opposite. Sure, I know, checkpatch --strict
>>> complains, but that is still better than unreadable code just to make
>>> checkpatch happy.
>>>
>>> Guenter
>>
>> Both seemed fine to me, the idea was to fix the checkpatch warning.
>> If it's OK for it to complain about this, plus the changes would make it
>> harder to read, please ignore this patch.
>>
>
> checkpatch is useful, but not in situations where following its guidance
> results in code which is diffficult to read. I run checkpatch --strict when
> applying patches, so I do notice when it complains. If I want a report
> to be addressed, I'll say that (such as, for example, when people are
> overly generous with empty lines). If not, you can assume that I am ok with
> the report and find it more important to have readable code than being
> checkpatch-clean.
>
> Guenter
That clears it up, thanks!
Aleksa
prev parent reply other threads:[~2023-04-12 5:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-09 18:35 Aleksa Savic
2023-04-10 16:53 ` Guenter Roeck
2023-04-11 18:26 ` Aleksa Savic
2023-04-11 20:19 ` Guenter Roeck
2023-04-12 5:18 ` Aleksa Savic [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9d8194bc-34d0-bbe9-825b-2b7635056a10@gmail.com \
--to=savicaleksa83@gmail.com \
--cc=jdelvare@suse.com \
--cc=leonard.anderweit@gmail.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=me@jackdoan.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®