From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: David Laight <David.Laight@aculab.com>
Cc: 'Philipp Gerlesberger' <Philipp.Gerlesberger@fau.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"ij72uhux@stud.informatik.uni-erlangen.de"
<ij72uhux@stud.informatik.uni-erlangen.de>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"linux-kernel@i4.cs.fau.de" <linux-kernel@i4.cs.fau.de>,
"sakari.ailus@linux.intel.com" <sakari.ailus@linux.intel.com>,
"mchehab@kernel.org" <mchehab@kernel.org>
Subject: Re: [PATCH v2 09/12] media: atomisp: Fix PARENTHESIS_ALIGNMENT
Date: Mon, 14 Dec 2020 14:56:49 +0100 [thread overview]
Message-ID: <X9dvIVc5evB8cfEr@kroah.com> (raw)
In-Reply-To: <61d5f8315efc42238a5516b1dc496760@AcuMS.aculab.com>
On Mon, Dec 14, 2020 at 11:49:56AM +0000, David Laight wrote:
> From: Philipp Gerlesberger
> > Sent: 14 December 2020 11:04
> >
> > You can sum up the two lines, because the maximum line length of
> > 100 columns is not exceeded.
>
> IIRC the 80 column limit is preferred.
Not anymore, checkpatch has changed.
next prev parent reply other threads:[~2020-12-14 13:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 11:03 [PATCH v2 09/12] media: atomisp: Fix PARENTHESIS_ALIGNMENT Philipp Gerlesberger
2020-12-14 11:03 ` [PATCH v2 10/12] media: atomisp: Fix BLOCK_COMMENT_STYLE Philipp Gerlesberger
2020-12-14 11:03 ` [PATCH v2 11/12] media: atomisp: Write function decleration in one line Philipp Gerlesberger
2020-12-14 11:03 ` [PATCH v2 12/12] media: atomisp: Fix LOGICAL_CONTINUATIONS Philipp Gerlesberger
2020-12-14 11:49 ` [PATCH v2 09/12] media: atomisp: Fix PARENTHESIS_ALIGNMENT David Laight
2020-12-14 13:56 ` gregkh [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-12-14 11:01 [PATCH v2 00/12] media: atomisp: Codingstyle Philipp Gerlesberger
2020-12-14 11:01 ` [PATCH v2 09/12] media: atomisp: Fix PARENTHESIS_ALIGNMENT Philipp Gerlesberger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=X9dvIVc5evB8cfEr@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=David.Laight@aculab.com \
--cc=Philipp.Gerlesberger@fau.de \
--cc=devel@driverdev.osuosl.org \
--cc=ij72uhux@stud.informatik.uni-erlangen.de \
--cc=linux-kernel@i4.cs.fau.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.