[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b23c180b-667e-4689-a7da-2f8b8902c8cc@roeck-us.net>
Date: Tue, 21 Mar 2023 07:35:34 -0700
From: Guenter Roeck <linux@...ck-us.net>
To: "andriy.shevchenko@...ux.intel.com"
<andriy.shevchenko@...ux.intel.com>
Cc: "Winiarska, Iwona" <iwona.winiarska@...el.com>,
"pmenzel@...gen.mpg.de" <pmenzel@...gen.mpg.de>,
"linux-hwmon@...r.kernel.org" <linux-hwmon@...r.kernel.org>,
"openbmc@...ts.ozlabs.org" <openbmc@...ts.ozlabs.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"jdelvare@...e.com" <jdelvare@...e.com>,
"fercerpav@...il.com" <fercerpav@...il.com>
Subject: Re: [PATCH] hwmon: (peci/cputemp) Fix miscalculated DTS for SKX
On Tue, Mar 21, 2023 at 03:08:45PM +0200, andriy.shevchenko@...ux.intel.com wrote:
> On Tue, Mar 21, 2023 at 10:29:22AM +0000, Winiarska, Iwona wrote:
> > On Tue, 2023-03-21 at 10:41 +0100, Paul Menzel wrote:
> > > Am 21.03.23 um 10:04 schrieb Iwona Winiarska:
>
> ...
>
> > > This is not aligned. Why not only use one space before the equal sign?
> >
> > Yeah - same alignment problem is present in cpu_hsx and cpu_icx though, so I
> > just followed along for skx to not stand out visually.
> > So while I agree that alignment is broken here, I think it might be better to
> > separate out the potential cleanup from the fix.
>
> I agree with Iwona. If community wants a cleanup, it can be created in
> a separate patch. For the fixes it's better to reduce the unrelated churn.
>
I don't want a cleanup. The original author chose the alignment,
I accepted it because I give submitters some slack when it comes to
formatting as long as checkpatch doesn't complain, and I do not want
to get into lets-change-alignment wars.
Thanks,
Guenter
Powered by blists - more mailing lists