All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Maxim Codita <maxkoditsa7c@gmail.com>
Cc: Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
	Teddy Wang <teddy.wang@siliconmotion.com>,
	linux-fbdev@vger.kernel.org, linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: sm750fb/sm750.c: mark g_def_fbmode as const pointer
Date: Wed, 12 Aug 2026 09:25:53 +0900	[thread overview]
Message-ID: <2026081233-simmering-exerciser-4ab2@gregkh> (raw)
In-Reply-To: <20260811130813.434660-1-maxkoditsa7c@gmail.com>

On Tue, Aug 11, 2026 at 03:08:13PM +0200, Maxim Codita wrote:
> Fix a checkpatch.pl warning for g_def_fbmode by marking the pointer
> as const. Ensures it is stored as read-only.
> 
> Note: g_fbmode[] is left as non-const as its elements are modified at
> runtime by lynxfb_set_fbinfo() and sm750fb_setup().
> 
> Signed-off-by: Maxim Codita <maxkoditsa7c@gmail.com>
> ---
>  drivers/staging/sm750fb/sm750.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/staging/sm750fb/sm750.c b/drivers/staging/sm750fb/sm750.c
> index 89c811e0806c..cc38dac88a73 100644
> --- a/drivers/staging/sm750fb/sm750.c
> +++ b/drivers/staging/sm750fb/sm750.c
> @@ -22,7 +22,7 @@ static int g_hwcursor = 1;
>  static int g_noaccel __ro_after_init;
>  static int g_nomtrr __ro_after_init;
>  static const char *g_fbmode[] = {NULL, NULL};
> -static const char *g_def_fbmode = "1024x768-32@60";
> +static const char  * const g_def_fbmode = "1024x768-32@60";

The spacing here looks very odd, don't you think?

And how was this tested?

thanks,

greg k-h

      reply	other threads:[~2026-08-12  0:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-11 13:08 [PATCH] staging: sm750fb/sm750.c: mark g_def_fbmode as const pointer Maxim Codita
2026-08-12  0:25 ` Greg Kroah-Hartman [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=2026081233-simmering-exerciser-4ab2@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=maxkoditsa7c@gmail.com \
    --cc=sudipm.mukherjee@gmail.com \
    --cc=teddy.wang@siliconmotion.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.