From: Greg KH <gregkh@linuxfoundation.org>
To: dipesh chaudhary <me@dipeshchaudhary.in>
Cc: sudipm.mukherjee@gmail.com, teddy.wang@siliconmotion.com,
linux-fbdev@vger.kernel.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: sm750fb: constify g_fbmode array
Date: Mon, 9 Mar 2026 10:56:01 +0100 [thread overview]
Message-ID: <2026030943-obscure-alive-fa6e@gregkh> (raw)
In-Reply-To: <9e566c42-8ec3-4d06-91be-0489de4e91c0@smtp-relay.sendinblue.com>
On Mon, Mar 09, 2026 at 09:49:57AM +0000, dipesh chaudhary wrote:
>
> Fix checkpatch warning for static const char array. Make the array of pointers read-only to improve memory safety.
>
> Signed-off-by: dipesh chaudhary <me@dipeshchaudhary.in>
> ---
> Makefile | 6 +++---
> drivers/staging/sm750fb/sm750.c | 2 +-
> 2 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/Makefile b/Makefile
> index df471d4212cc..e944c6e71e81 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -1,8 +1,8 @@
> # SPDX-License-Identifier: GPL-2.0
> -VERSION = 6
> -PATCHLEVEL = 19
> +VERSION = 7
> +PATCHLEVEL = 0
> SUBLEVEL = 0
> -EXTRAVERSION =
> +EXTRAVERSION = -rc1
> NAME = Baby Opossum Posse
>
> # *DOCUMENTATION*
Why have you changed the Makefile?
And did you test-build your change?
thanks,
greg k-h
next parent reply other threads:[~2026-03-09 9:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9e566c42-8ec3-4d06-91be-0489de4e91c0@smtp-relay.sendinblue.com>
2026-03-09 9:56 ` Greg KH [this message]
2026-03-09 10:13 [PATCH] staging: sm750fb: constify g_fbmode array dipesh chaudhary
-- strict thread matches above, loose matches on Subject: below --
2026-03-09 10:06 dipesh chaudhary
2026-03-09 9:49 dipesh chaudhary
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=2026030943-obscure-alive-fa6e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=me@dipeshchaudhary.in \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox