From: Joe Perches <joe@perches.com>
To: Patryk Kocielnik <patryk.kocielnik@gmail.com>,
sudipm.mukherjee@gmail.com
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: sm750fb: sm750: fixed coding style issues
Date: Wed, 22 Nov 2017 08:03:24 -0800 [thread overview]
Message-ID: <1511366604.6989.93.camel@perches.com> (raw)
In-Reply-To: <20171122154226.9493-1-patryk.kocielnik@gmail.com>
On Wed, 2017-11-22 at 16:42 +0100, Patryk Kocielnik wrote:
> Cleaned checkpatch warnings by fixing coding style issues.
checkpatch is not always correct.
> Signed-off-by: Patryk Kocielnik <patryk.kocielnik@gmail.com>
> ---
> drivers/staging/sm750fb/sm750.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/staging/sm750fb/sm750.c b/drivers/staging/sm750fb/sm750.c
[]
> @@ -32,7 +32,7 @@
> static int g_hwcursor = 1;
> static int g_noaccel;
> static int g_nomtrr;
> -static const char *g_fbmode[] = {NULL, NULL};
> +static const char * const g_fbmode[] = {NULL, NULL};
Make sure you compile any file modified by a patch
_before_ submitting the proposed patch.
> static const char *g_def_fbmode = "1024x768-32@60";
> static char *g_settings;
> static int g_dualview;
> @@ -749,7 +749,7 @@ static int lynxfb_set_fbinfo(struct fb_info *info, int index)
> lynx750_ext, NULL, vesa_modes,
> };
> int cdb[] = {ARRAY_SIZE(lynx750_ext), 0, VESA_MODEDB_SIZE};
> - static const char *mdb_desc[] = {
> + static const char * const mdb_desc[] = {
> "driver prepared modes",
> "kernel prepared default modedb",
> "kernel HELPERS prepared vesa_modes",
next prev parent reply other threads:[~2017-11-22 16:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-22 15:42 [PATCH] Staging: sm750fb: sm750: fixed coding style issues Patryk Kocielnik
2017-11-22 16:03 ` Joe Perches [this message]
[not found] ` <CAGU7hBg+=QbhsS+eMiAhQTtr_R1B4u9hfyOH5KkGRSYat=fJSg@mail.gmail.com>
2017-11-22 17:35 ` Patryk Kocielnik
2017-11-22 17:45 ` 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=1511366604.6989.93.camel@perches.com \
--to=joe@perches.com \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patryk.kocielnik@gmail.com \
--cc=sudipm.mukherjee@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.