[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a2a3ab35-7e21-51f9-fee2-67f6686b13c8@roeck-us.net>
Date: Sun, 27 Mar 2022 16:25:00 -0700
From: Guenter Roeck <linux@...ck-us.net>
To: Eugene Shalygin <eugene.shalygin@...il.com>
Cc: darcagn@...tonmail.com, Jean Delvare <jdelvare@...e.com>,
linux-hwmon@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/4] hwmon: (asus-ec-sensors) implement locking via the
ACPI global lock
On 3/27/22 11:51, Eugene Shalygin wrote:
> On Sun, 27 Mar 2022 at 20:04, Guenter Roeck <linux@...ck-us.net> wrote:
>
>> What is the problem other than that the string is split across
>> multiple lines ? That can easily be fixed by not splitting it,
>> so you'll have to be more specific.
>
> Yes, the problem is that it is split. When merged it exceeds the 80-th
> column and creates problems for editors instructed to format text on
> paste. And I would not like to neither split the string onto two debug
> messages, nor shorten the debug message itself. Maybe there is an
> elegant solution I'm not aware of?
>
First, you can go up to 100 columns nowadays. Second, the column
limit is waived for strings because it is more important to not
split them. If you _still_ want to stick with 80 columns, sorry,
no, I don't have a solution. Your problem is with the editor,
not with kernel formatting rules.
Guenter
Powered by blists - more mailing lists