From: David Laight <David.Laight@ACULAB.COM>
To: 'Philipp Gerlesberger' <Philipp.Gerlesberger@fau.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "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>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"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 11:49:56 +0000 [thread overview]
Message-ID: <61d5f8315efc42238a5516b1dc496760@AcuMS.aculab.com> (raw)
In-Reply-To: <20201214110358.7102-10-Philipp.Gerlesberger@fau.de>
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.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2020-12-14 11:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 11:03 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 ` David Laight [this message]
2020-12-14 13:56 ` [PATCH v2 09/12] media: atomisp: Fix PARENTHESIS_ALIGNMENT gregkh
-- 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=61d5f8315efc42238a5516b1dc496760@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=Philipp.Gerlesberger@fau.de \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®