Linux Framebuffer Layer development
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <syrjala@sci.fi>
To: H Hartley Sweeten <hartleys@visionengravers.com>
Cc: Mikulas Patocka <mpatocka@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [PATCH 3/3] atyfb: Coding style cleanup
Date: Tue, 23 Jun 2009 20:30:22 +0300	[thread overview]
Message-ID: <20090623173022.GD9980@sci.fi> (raw)
In-Reply-To: <BD79186B4FD85F4B8E60E381CAEE1909019BDCF8@mi8nycmail19.Mi8.com>

On Tue, Jun 23, 2009 at 12:52:58PM -0400, H Hartley Sweeten wrote:
> On Saturday, June 20, 2009 2:30 PM, Ville Syrjala wrote:
> > Fix a bunch of coding style problems in atyfb_base.c.
> > 
> > Signed-off-by: Ville Syrjala <syrjala@sci.fi>
> > ---
> > There are still some problems left, at least over 80 char lines, but
> > fixing those in a decent manner would require some code restructuring
> > to reduce the overly deep nesting. I decided to leave those bits mostly
> > untouched for now.
> > 
> >  drivers/video/aty/atyfb_base.c |  829 ++++++++++++++++++++++------------------
> >  1 files changed, 458 insertions(+), 371 deletions(-)
> > 
> > diff --git a/drivers/video/aty/atyfb_base.c b/drivers/video/aty/atyfb_base.c
> > index 63d3739..913b4a4 100644
> > --- a/drivers/video/aty/atyfb_base.c
> > +++ b/drivers/video/aty/atyfb_base.c
> > @@ -132,7 +132,7 @@
> >  #endif
> >  
> >  #define PRINTKI(fmt, args...)	printk(KERN_INFO "atyfb: " fmt, ## args)
> > -#define PRINTKE(fmt, args...)	 printk(KERN_ERR "atyfb: " fmt, ## args)
> > +#define PRINTKE(fmt, args...)	printk(KERN_ERR "atyfb: " fmt, ## args)
> 
> Why not: 
> 
> #define pr_fmt(fmt)	"atyfb: " fmt
> 
> Then just use pr_info() and pr_err()?  Also, pr_devel() could be used instead
> of the private DPRINTK() definition.

Ideally it should use dev_info(), dev_err() and dev_dbg() but at the
moment I have no motivation to start cleaning up the printk mess in
this driver.

-- 
Ville Syrjälä
syrjala@sci.fi
http://www.sci.fi/~syrjala/

------------------------------------------------------------------------------

  reply	other threads:[~2009-06-23 17:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-20 21:29 [PATCH 1/3] atyfb: Fix HP OmniBook 500 reboot hang Ville Syrjala
2009-06-20 21:29 ` [PATCH 2/3] atyfb: Fix alignment for block writes Ville Syrjala
2009-06-22 23:13   ` Mikulas Patocka
2009-06-20 21:29 ` [PATCH 3/3] atyfb: Coding style cleanup Ville Syrjala
2009-06-23 16:52   ` H Hartley Sweeten
2009-06-23 17:30     ` Ville Syrjälä [this message]
2009-06-23 18:20       ` H Hartley Sweeten

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=20090623173022.GD9980@sci.fi \
    --to=syrjala@sci.fi \
    --cc=akpm@linux-foundation.org \
    --cc=hartleys@visionengravers.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=mpatocka@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