[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190823112607.1b4a69bf@cakuba.netronome.com>
Date: Fri, 23 Aug 2019 11:26:07 -0700
From: Jakub Kicinski <jakub.kicinski@...ronome.com>
To: Vlad Buslov <vladbu@...lanox.com>
Cc: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"jhs@...atatu.com" <jhs@...atatu.com>,
"xiyou.wangcong@...il.com" <xiyou.wangcong@...il.com>,
"jiri@...nulli.us" <jiri@...nulli.us>,
"davem@...emloft.net" <davem@...emloft.net>,
"pablo@...filter.org" <pablo@...filter.org>,
Jiri Pirko <jiri@...lanox.com>, linux-doc@...r.kernel.org
Subject: Re: [PATCH net-next 03/10] net: sched: refactor block offloads
counter usage
On Fri, 23 Aug 2019 10:39:50 +0000, Vlad Buslov wrote:
> >> +/* Destroy filter and decrement block offload counter, if filter was previously
> >> + * offloaded.
> >> + */
> >> +
> >
> > hm.. is this gap between comment and function it pertains to
> > intentional?
>
> Majority of function comments in cls_api.c have newline after them (not
> all of them though). I don't have any strong opinions regarding this.
> You suggest it is better not to have blank lines after function
> comments?
Ah, you're right. I think it's pretty strange to have a new line after
a comment which pertains only to the function which is immediately
following it. Often the new line is used as a separation, when the
comment describes whole section of the file..
I kind of wish kdoc allowed none of the parameters to be described.
Often you want to document the function but the parameters are kind
of obvious.
Anyway... feel free to leave this as is.
Powered by blists - more mailing lists