linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Krzysztof Helt <krzysztof.h1@poczta.fm>
Cc: JosephChan@via.com.tw, geert@linux-m68k.org,
	linux-fbdev-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [Linux-fbdev-devel] [PATCH 1/9] viafb: VIA Frame Buffer Device Driver - Resend
Date: Wed, 7 May 2008 14:03:57 -0700	[thread overview]
Message-ID: <20080507140357.9320dfcd.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080507184333.7d0f1bf4.krzysztof.h1@poczta.fm>

On Wed, 7 May 2008 18:43:33 +0200
Krzysztof Helt <krzysztof.h1@poczta.fm> wrote:

> A general comment is that you use to many global variables.

yes, that was my first impression.  The _names_ of those variables is a
real problem.  lcd_mode, DeviceStatus, second_size, primary_dev, etc.  The
driver is attempting to reserve all those names for itself, kernel-wide.

So at a minimum, going through and prepending viafb_ onto all those would
be needed.


There are a number of layout glitches in there.  Such as a strange combination of
two styles:

void foo(void)
{

versus

void foo(void ) {

Many of these things can be pinpointed by processing the diff with
scripts/checkpatch.pl.


Administrative note: all nine patches had the same title "viafb: VIA Frame
Buffer Device Driver".  Please choose unique and meaningful names for each
patch, such as "viafb: add utility header file".


Apart from those fairly easily-fixed things, the driver looks pretty good
from a quick scan, given how large it is, and given that it probably has
been around for quite a long time..

  reply	other threads:[~2008-05-07 21:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-07 11:06 [PATCH 1/9] viafb: VIA Frame Buffer Device Driver - Resend JosephChan
2008-05-07 16:43 ` [Linux-fbdev-devel] " Krzysztof Helt
2008-05-07 21:03   ` Andrew Morton [this message]
2008-05-08  0:58     ` JosephChan
2008-05-08 13:24       ` [Linux-fbdev-devel] " Pekka Enberg
2008-05-08  0:51   ` JosephChan
2008-05-08  8:15   ` Ondrej Zajicek
2008-05-08 12:52     ` [Linux-fbdev-devel] " Geert Uytterhoeven
2008-05-16 20:22       ` Luc Verhaegen

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=20080507140357.9320dfcd.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=JosephChan@via.com.tw \
    --cc=geert@linux-m68k.org \
    --cc=krzysztof.h1@poczta.fm \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    /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).