linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert William Fuller <hydrologiccycle@gmail.com>
To: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: "Shah, Hardik" <hardik.shah@ti.com>,
	"video4linux-list@redhat.com" <video4linux-list@redhat.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"linux-fbdev-devel@lists.sourceforge.net"
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [PATCH] OMAP 2/3 V4L2 display driver on video planes
Date: Sun, 05 Oct 2008 07:57:20 -0400	[thread overview]
Message-ID: <48E8ABA0.8070305@gmail.com> (raw)
In-Reply-To: <20081005081931.1dfdd7b4@pedra.chehab.org>

Mauro Carvalho Chehab wrote:
> On Fri, 3 Oct 2008 20:10:36 +0530
> "Shah, Hardik" <hardik.shah@ti.com> wrote:
>>> 3) Some of the lines are broken up rather badly probably to respect the
>>> 80 column maximum. Note that the 80 column maximum is a recommendation,
>>> and that readability is more important. So IMHO it's better to have a
>>> slightly longer line and break it up at a more logical place. However,
>>> switching to video_ioctl2 will automatically reduce the indentation, so
>>> this might not be that much of an issue anymore.
>> [Shah, Hardik] 80 column was implemented to make the checkpatch pass.  Point noted and will take care of this.
> 
> The 80 column rule isn't there for nothing.

The 80 column rule is retarded.  None of this code needs to fit on punch 
cards, nor is it COBOL.  There are legitimate reasons to have lines 
longer than 80 columns.  No matter how simple a program is, it is likely 
to have an expression that is longer than 80 characters.  Most people's 
displays are wider than 80 columns these days.  Vertical real estate is 
at a greater premium than horizontal real estate these days with wider 
aspect ratio monitors, which better approximate the human field of 
vision.  Why make people scan more than one line for a single expression?


  reply	other threads:[~2008-10-05 11:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-17 15:05 [PATCH] OMAP 2/3 V4L2 display driver on video planes Hardik Shah
2008-09-17 15:30 ` Sakari Ailus
2008-09-17 15:42   ` Hiremath, Vaibhav
2008-10-03 14:33 ` Hans Verkuil
2008-10-03 14:40   ` Shah, Hardik
2008-10-05 11:19     ` Mauro Carvalho Chehab
2008-10-05 11:57       ` Robert William Fuller [this message]
2008-10-05 12:05         ` Mauro Carvalho Chehab
2008-10-07 21:48         ` [Linux-fbdev-devel] " Krzysztof Helt
2008-10-06  6:06       ` Shah, Hardik
2008-10-06  6:29         ` Hans Verkuil
2008-10-06  8:41           ` Måns Rullgård
2008-10-06  8:50           ` Shah, Hardik
2008-10-06 11:22             ` [Linux-fbdev-devel] " Geert Uytterhoeven
2008-10-24  9:50           ` Shah, Hardik

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=48E8ABA0.8070305@gmail.com \
    --to=hydrologiccycle@gmail.com \
    --cc=hardik.shah@ti.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-omap@vger.kernel.org \
    --cc=mchehab@infradead.org \
    --cc=video4linux-list@redhat.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;
as well as URLs for NNTP newsgroup(s).