[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <84b4db0f2c82adbd82e2b93f5b1511730cb0678e.camel@perches.com>
Date: Tue, 13 Apr 2021 10:43:24 -0700
From: Joe Perches <joe@...ches.com>
To: Dwaipayan Ray <dwaipayanray1@...il.com>,
Thierry Reding <thierry.reding@...il.com>
Cc: Aline Santana Cordeiro <alinesantanacordeiro@...il.com>,
Andy Whitcroft <apw@...onical.com>,
Lukas Bulwahn <lukas.bulwahn@...il.com>,
Dmitry Osipenko <digetx@...il.com>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jonathan Hunter <jonathanh@...dia.com>,
linux-media@...r.kernel.org, linux-staging@...ts.linux.dev,
linux-kernel <linux-kernel@...r.kernel.org>,
outreachy-kernel@...glegroups.com
Subject: Re: [PATCH] staging: media: tegra-vde: Align line break to match
with the open parenthesis in file trace.h
On Tue, 2021-04-13 at 21:35 +0530, Dwaipayan Ray wrote:
> On Tue, Apr 13, 2021 at 8:59 PM Thierry Reding <thierry.reding@...il.com> wrote:
> >
> > On Mon, Apr 12, 2021 at 07:20:40PM -0300, Aline Santana Cordeiro wrote:
> > > Align line break to match with the open parenthesis.
> > > Issue detected by checkpatch.pl.
> > > It consequently solved a few end lines with a '(',
> > > issue also detected by checkpatch.pl
> > >
> > > Signed-off-by: Aline Santana Cordeiro <alinesantanacordeiro@...il.com>
> > > ---
> > > drivers/staging/media/tegra-vde/trace.h | 111 ++++++++++++++------------------
> > > 1 file changed, 50 insertions(+), 61 deletions(-)
> >
> > Ugh... I'd say this is one case where checkpatch.pl really shouldn't be
> > complaining since this isn't a function call or declaration. It's more
> > like a code snippet written with macros, so I don't think the same rules
> > should apply.
> >
> > Adding checkpatch folks (hence quoting in full): is there anything we
> > can do about this without too much effort? Or should we just accept this
> > the way it is?
> >
>
> While it may be possible to add exceptions for trace headers on the
> alignment rules, I don't know how many more such exceptions we will
> end up adding. Such fine grained checks might be unnecessarily complex.
> So I think we should just accept the way it is for now.
>
> Joe might have a different opinion?
Tracing uses a different style.
Maybe just suppress various messages for complete code blocks
of DECLARE_EVENT_CLASS, DEFINE_EVENT, and TRACE_EVENT
Powered by blists - more mailing lists