[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210416085431.GM3@paasikivi.fi.intel.com>
Date: Fri, 16 Apr 2021 11:54:32 +0300
From: Sakari Ailus <sakari.ailus@...ux.intel.com>
To: Julia Lawall <julia.lawall@...ia.fr>
Cc: Dan Carpenter <dan.carpenter@...cle.com>,
Matthew Wilcox <willy@...radead.org>,
Aline Santana Cordeiro <alinesantanacordeiro@...il.com>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-media@...r.kernel.org, linux-staging@...ts.linux.dev,
linux-kernel@...r.kernel.org, outreachy-kernel@...glegroups.com
Subject: Re: [Outreachy kernel] [PATCH v2] staging: media: atomisp: pci:
Change line break to avoid an open parenthesis at the end of the line
On Fri, Apr 16, 2021 at 10:46:54AM +0200, Julia Lawall wrote:
> > > If you're running into the 80 character limit, then it's fine to use
> > > two tabs. I think we have been rejecting patches that push align the
> > > parameters but push past the 80 character limit. Using one tab is
> > > confusing because it makes the decalarations line up with the code.
> >
> > Interesting. Do you have an example of this? I've thought checkpatch.pl
> > gave a warning if the line ended with an opening parenthesis no matter
> > what.
>
> Checkpatch is a perl script that searches for patterns that often indicate
> code that is hard to understand. It is not a precise definition of what
> is allowed in the Linux kernel. Humans have to amke compromises.
Yeah... but I'd think if this is a preferred style then the warning could
be omitted. It might not be that difficult.
--
Sakari Ailus
Powered by blists - more mailing lists