mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shiva Kerdel <shiva@exdev.nl>
To: arnaud.patard@rtp-net.org
Cc: gregkh@linuxfoundation.org, namrataashettar@gmail.com,
	bhumirks@gmail.com, benoit.hiller@gmail.com, aquannie@gmail.com,
	clifton.a.barnes@gmail.com, janani.rvchndrn@gmail.com,
	bmarsh94@gmail.com, maninder.s2@samsung.com,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
	Shiva Kerdel <shiva@exdev.nl>
Subject: [PATCH] Staging: xgifb: vgatypes: Replace decimal permissions with 4 digit octal
Date: Tue,  8 Nov 2016 17:14:27 +0100	[thread overview]
Message-ID: <20161108161427.17193-1-shiva@exdev.nl> (raw)

Replaced decimal permissions with 4 digit octal to solve checkpatch errors.

Signed-off-by: Shiva Kerdel <shiva@exdev.nl>
---
 drivers/staging/xgifb/XGI_main_26.c | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/drivers/staging/xgifb/XGI_main_26.c b/drivers/staging/xgifb/XGI_main_26.c
index 89bd4dd..982f90f 100644
--- a/drivers/staging/xgifb/XGI_main_26.c
+++ b/drivers/staging/xgifb/XGI_main_26.c
@@ -2058,19 +2058,19 @@ static struct pci_driver xgifb_driver = {
 /*                      MODULE                       */
 /*****************************************************/
 
-module_param(mode, charp, 0);
+module_param(mode, charp, 0000);
 MODULE_PARM_DESC(mode,
 	"Selects the desired default display mode in the format XxYxDepth (eg. 1024x768x16).");
 
-module_param(forcecrt2type, charp, 0);
+module_param(forcecrt2type, charp, 0000);
 MODULE_PARM_DESC(forcecrt2type,
 	"Force the second display output type. Possible values are NONE, LCD, TV, VGA, SVIDEO or COMPOSITE.");
 
-module_param(vesa, int, 0);
+module_param(vesa, int, 0000);
 MODULE_PARM_DESC(vesa,
 	"Selects the desired default display mode by VESA mode number (eg. 0x117).");
 
-module_param(filter, int, 0);
+module_param(filter, int, 0000);
 MODULE_PARM_DESC(filter,
 	"Selects TV flicker filter type (only for systems with a SiS301 video bridge). Possible values 0-7. Default: [no filter]).");
 
-- 
2.10.2

                 reply	other threads:[~2016-11-08 16:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20161108161427.17193-1-shiva@exdev.nl \
    --to=shiva@exdev.nl \
    --cc=aquannie@gmail.com \
    --cc=arnaud.patard@rtp-net.org \
    --cc=benoit.hiller@gmail.com \
    --cc=bhumirks@gmail.com \
    --cc=bmarsh94@gmail.com \
    --cc=clifton.a.barnes@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=janani.rvchndrn@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maninder.s2@samsung.com \
    --cc=namrataashettar@gmail.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

Powered by JetHome