From: Joe Perches <joe@perches.com>
To: Jacopo Mondi <jacopo@jmondi.org>
Cc: "Krzysztof Hałasa" <khalasa@piap.pl>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Rob Herring" <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
"Sakari Ailus" <sakari.ailus@iki.fi>
Subject: Re: [PATCH v6 2/2] Driver for ON Semi AR0521 camera sensor
Date: Thu, 23 Dec 2021 12:13:10 -0800 [thread overview]
Message-ID: <02c71d9fe95f72c5aa5a01adadda8fb7e756fae1.camel@perches.com> (raw)
In-Reply-To: <20211223184856.v34ecibwzepahsju@uno.localdomain>
On Thu, 2021-12-23 at 19:48 +0100, Jacopo Mondi wrote:
> The media subsystem requires to validate patches with
>
> ./scripts/checkpatch.pl --strict --max-line-length=80
>
> We longly debated this and I believe it's now generally accepted to go
> over 80 when it makes sense, but not regularly span to 120 cols like
> in the previous version.
Where is this documented and do you have a link to the debate?
The archive for the i2c mailing list doesn't show much debate:
https://lore.kernel.org/linux-i2c/?q=%2280+columns%22
https://lore.kernel.org/linux-i2c/?q=%22line+length%22
Perhaps there should be a MAINTAINERS P: entry for this requirement.
From MAINTAINERS:
P: Subsystem Profile document for more details submitting
patches to the given subsystem. This is either an in-tree file,
or a URI. See Documentation/maintainer/maintainer-entry-profile.rst
for details.
next prev parent reply other threads:[~2021-12-23 20:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-23 6:54 [PATCH v6 0/2] On Semi AR0521 sensor driver Krzysztof Hałasa
2021-12-23 6:57 ` [PATCH v6 1/2] dt-binding: media: document ON Semi AR0521 sensor bindings Krzysztof Hałasa
2021-12-23 7:06 ` [PATCH v6 2/2] Driver for ON Semi AR0521 camera sensor Krzysztof Hałasa
2021-12-23 17:49 ` Joe Perches
2021-12-23 18:48 ` Jacopo Mondi
2021-12-23 19:19 ` Joe Perches
2021-12-23 20:13 ` Joe Perches [this message]
2021-12-23 20:27 ` Joe Perches
2021-12-24 9:22 ` Jacopo Mondi
2021-12-24 12:30 ` Joe Perches
2021-12-29 15:05 ` Krzysztof Hałasa
2021-12-29 14:11 ` Krzysztof Hałasa
2021-12-31 23:14 ` kernel test robot
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=02c71d9fe95f72c5aa5a01adadda8fb7e756fae1.camel@perches.com \
--to=joe@perches.com \
--cc=devicetree@vger.kernel.org \
--cc=jacopo@jmondi.org \
--cc=khalasa@piap.pl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=robh+dt@kernel.org \
--cc=sakari.ailus@iki.fi \
/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®