public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
	Himanshu Jha <himanshujha199640@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-fbdev@vger.kernel.org
Subject: Re: [PATCH] drivers: video: Fix 80 character limit and remove unnecessary space
Date: Wed, 23 Aug 2017 14:32:42 -0700	[thread overview]
Message-ID: <1503523962.6933.15.camel@perches.com> (raw)
In-Reply-To: <5135691.E4iXgiitH9@amdc3058>

On Wed, 2017-08-23 at 18:12 +0200, Bartlomiej Zolnierkiewicz wrote:
> Hi,
> 
> Please use a more descriptive patch subject, i.e.
> "fbdev: vgastate: fix checkpatch.pl reported warnings".
> 
> Please also cc: fbdev mailing list (linux-fbdev@vger.kernel.org
> on fbdev patches).
> 
> On Monday, August 21, 2017 07:33:51 PM Himanshu Jha wrote:
> > Fixes the following checkpatch warnings:
> > WARNING: line over 80 characters
> > WARNING: space prohibited between function name and open parenthesis '('
> > WARNING: EXPORT_SYMBOL(foo); should immediately follow its function/variable
[]
> > diff --git a/drivers/video/vgastate.c b/drivers/video/vgastate.c
[]
> > @@ -31,8 +31,9 @@ struct regstate {
> >  	__u8 misc;
> >  };
> >  
> > -static inline unsigned char vga_rcrtcs(void __iomem *regbase, unsigned short iobase,
> > -				       unsigned char reg)
> > +static inline unsigned char vga_rcrtcs(void __iomem *regbase,
> > +						unsigned short iobase,
> > +							unsigned char reg)
> 
> This is not an improvement and doesn't conform to the kernel CodingStyle.
> 
> It should be:
> 
> static inline unsigned char vga_rcrtcs(void __iomem *regbase,
> 				       unsigned short iobase,
> 				       unsigned char reg)
> 
> >  {
> >  	vga_w(regbase, iobase + 0x4, reg);
> >  	return vga_r(regbase, iobase + 0x5);

Better to remove the inline and let the compiler decide too.

Perhaps:

static unsigned char vga_rcrtcs(void __iomem *regbase, unsigned short iobase,
				unsigned char reg)

      reply	other threads:[~2017-08-23 23:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20170821140419epcas1p44df6f964a3977e1305cd4845cfcef783@epcas1p4.samsung.com>
2017-08-21 14:03 ` [PATCH] drivers: video: Fix 80 character limit and remove unnecessary space Himanshu Jha
2017-08-23 16:12   ` Bartlomiej Zolnierkiewicz
2017-08-23 21:32     ` Joe Perches [this message]

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=1503523962.6933.15.camel@perches.com \
    --to=joe@perches.com \
    --cc=b.zolnierkie@samsung.com \
    --cc=himanshujha199640@gmail.com \
    --cc=linux-fbdev@vger.kernel.org \
    --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