[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210415195704.GE2531743@casper.infradead.org>
Date: Thu, 15 Apr 2021 20:57:04 +0100
From: Matthew Wilcox <willy@...radead.org>
To: Sakari Ailus <sakari.ailus@...ux.intel.com>
Cc: 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 Thu, Apr 15, 2021 at 10:49:55PM +0300, Sakari Ailus wrote:
> On Thu, Apr 15, 2021 at 06:14:09PM +0100, Matthew Wilcox wrote:
> > On Thu, Apr 15, 2021 at 02:08:19PM -0300, Aline Santana Cordeiro wrote:
> > > -const struct atomisp_format_bridge *get_atomisp_format_bridge_from_mbus(
> > > - u32 mbus_code);
> > > +const struct atomisp_format_bridge*
> > > +get_atomisp_format_bridge_from_mbus(u32 mbus_code);
> >
> > No, this does not match coding style. Probably best to break the
> > 80-column guideline in this instance. Best would be to have a function
>
> Having the return type on the previous line is perfectly fine. There should
> be a space before the asterisk though.
No, it's not. Linus has ranted about that before.
Powered by blists - more mailing lists