linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
To: 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 16:12:41 +0000	[thread overview]
Message-ID: <5135691.E4iXgiitH9@amdc3058> (raw)
In-Reply-To: <1503324231-10675-1-git-send-email-himanshujha199640@gmail.com>


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
> 
> Signed-off-by: Himanshu Jha <himanshujha199640@gmail.com>
> ---
>  drivers/video/vgastate.c | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)
> 
> diff --git a/drivers/video/vgastate.c b/drivers/video/vgastate.c
> index 548c751..a52283d 100644
> --- 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);
> @@ -454,8 +455,9 @@ int save_vga(struct vgastate *state)
>  	}
>  	return 0;
>  }
> +EXPORT_SYMBOL(save_vga);
>  
> -int restore_vga (struct vgastate *state)
> +int restore_vga(struct vgastate *state)
>  {
>  	if (state->vidstate = NULL)
>  		return 1;
> @@ -480,8 +482,6 @@ int restore_vga (struct vgastate *state)
>  	vga_cleanup(state);
>  	return 0;
>  }
> -
> -EXPORT_SYMBOL(save_vga);
>  EXPORT_SYMBOL(restore_vga);
>  
>  MODULE_AUTHOR("James Simmons <jsimmons@users.sf.net>");

Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics


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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20170821140419epcas1p44df6f964a3977e1305cd4845cfcef783@epcas1p4.samsung.com>
     [not found] ` <1503324231-10675-1-git-send-email-himanshujha199640@gmail.com>
2017-08-23 16:12   ` Bartlomiej Zolnierkiewicz [this message]
2017-08-23 21:32     ` [PATCH] drivers: video: Fix 80 character limit and remove unnecessary space Joe Perches

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=5135691.E4iXgiitH9@amdc3058 \
    --to=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;
as well as URLs for NNTP newsgroup(s).