[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yh+WJpmVe6V2oJVT@smile.fi.intel.com>
Date: Wed, 2 Mar 2022 18:07:02 +0200
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Daniel Lezcano <daniel.lezcano@...aro.org>
Cc: shruthi.sanil@...el.com, tglx@...utronix.de, robh+dt@...nel.org,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
mgross@...ux.intel.com, srikanth.thokala@...el.com,
lakshmi.bai.raja.subramanian@...el.com,
mallikarjunappa.sangannavar@...el.com
Subject: Re: [PATCH v8 2/2] clocksource: Add Intel Keem Bay timer support
On Wed, Mar 02, 2022 at 04:58:08PM +0100, Daniel Lezcano wrote:
> On 02/03/2022 14:53, Andy Shevchenko wrote:
> > On Tue, Mar 01, 2022 at 10:09:06PM +0100, Daniel Lezcano wrote:
> > > On 22/02/2022 10:56, shruthi.sanil@...el.com wrote:
...
> > > One line comment format is usually for the network subsystem
> > Any pointers to the documentation, please?
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/coding-style.rst#n598
>
> Well actually it is for multi line, so I may have confused with these one
> line comments.
Seems so.
> On the other hand having one line comment telling what does the function
> right after is not really useful. The function names are self-explanatory.
Agree on this.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists