[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c09401d003360cff41c949ccaea8ae9dc7b2c733.camel@perches.com>
Date: Fri, 18 Dec 2020 02:08:39 -0800
From: Joe Perches <joe@...ches.com>
To: David Laight <David.Laight@...LAB.COM>,
Daniel West <daniel.west.dev@...il.com>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>
Cc: "hverkuil-cisco@...all.nl" <hverkuil-cisco@...all.nl>,
"mchehab+huawei@...nel.org" <mchehab+huawei@...nel.org>,
"christian.gromm@...rochip.com" <christian.gromm@...rochip.com>,
"masahiroy@...nel.org" <masahiroy@...nel.org>,
"devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] staging: most: video: fixed a parentheses coding style
issue.
On Fri, 2020-12-18 at 09:49 +0000, David Laight wrote:
> From: Joe Perches
> > Sent: 17 December 2020 23:58
> >
> > On Thu, 2020-12-17 at 15:45 -0800, Daniel West wrote:
> > > Fixed a coding style issue.
> >
> > It may pass checkpatch without warning, but it's uncommon kernel coding style.
>
> checkpatch probably shouldn't complain about lines that end in (
> if they are function definitions.
Opinons vary.
Very few function declaration/definitions in the linux kernel use the
one line per argument style (gnu indent -bfde)
type function(
type argument1,
type argument2,
...
)
{
...
}
It probably shouldn't be encouraged.
> > or (> 80 columns)
> > static struct most_video_dev *get_comp_dev(struct most_interface *iface, int channel_idx)
> Or shorten the variable/type names a bit so it all fits.
Always a possibility but probably not a good one here as even
renaming channel_idx to idx doesn't make it < 80 columns
Powered by blists - more mailing lists