linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [PATCH] savagefb: vsync for twisterP
Date: Wed, 20 Dec 2006 08:37:35 -0800	[thread overview]
Message-ID: <20061220083735.84ea3c5f.randy.dunlap@oracle.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0612201059100.2728@localhost.localdomain>

On Wed, 20 Dec 2006 10:59:32 +0100 (CET) Mark Pustjens wrote:

> Ofcourse, I have to actually *add* the patch :)

Preferably not as an attachment, but as inline text.
Pine can usually do that without problems.


> On Wed, 20 Dec 2006, Mark Pustjens wrote:
> 
> > Hi,
> >
> > This patch add support to the savagefb driver for
> > waiting for vsync for the TwisterP chipset.
> >
> > The patch adds an ioctl FBIO_WAITFORVSYNC just like the
> > matroxfb driver.
> >
> > It probably needs some work.

Here are some comments.

1.  Use tabs consistently for indentation.  The patch has lots
of mixed spaces/tabs, e.g.:

+	struct savagefb_par *par = dev_id;
+        u_int32_t status;
+        int handled = 0;
+	unsigned char b;

2.  Function opening brace goes on a line by itself, not like this
(and other places):

+int savagefb_enable_irq(struct fb_info *info, int reenable) {

3.  Use new irq request names.  This:

+                if (request_irq(par->pcidev->irq, savagefb_irq,
+                                SA_SHIRQ, "savagefb", par)) {

should use IRQF_SHARED instead of SA_SHIRQ.
See comment in linux/interrupt.h:

/*
 * Migration helpers. Scheduled for removal in 1/2007
 * Do not use for new code !
 */

4.  Try to keep source lines < 80 columns so that they are
easily readable in a term window.

5.  Linux switch/case style puts 'case' at the same indent
level as 'switch' to save on indentation.

6.  Don't wrap one-line if-s in braces.  I.e., drop these and
similar braces (and use tabs to indent):

+        if (ret) {
+                return ret;
+        }

7.  Use /* ... */ comment style, not // style.

8.  s/treshold/threshold/ (typo/spello)

---
~Randy

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

  reply	other threads:[~2006-12-20 16:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-20  9:38 [PATCH] savagefb: vsync for twisterP Mark Pustjens
2006-12-20  9:59 ` Mark Pustjens
2006-12-20 16:37   ` Randy Dunlap [this message]
2007-01-09 11:12     ` Mark Pustjens

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=20061220083735.84ea3c5f.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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).