mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Robin van der Gracht <robin@protonic.nl>
To: Nishka Dasgupta <nishkadg.linux@gmail.com>
Cc: miguel.ojeda.sandonis@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] auxdisplay: ht16k33: Make ht16k33_fb_fix and ht16k33_fb_var constant
Date: Tue, 20 Aug 2019 08:28:29 +0200	[thread overview]
Message-ID: <894371cda58112ee77cc0c8a5d336d2d@protonic.nl> (raw)
In-Reply-To: <20190819075126.870-1-nishkadg.linux@gmail.com>

On 2019-08-19 09:51, Nishka Dasgupta wrote:
> The static structures ht16k33_fb_fix and ht16k33_fb_var, of types
> fb_fix_screeninfo and fb_var_screeninfo respectively, are not used
> except to be copied into other variables. Hence make both of them
> constant to prevent unintended modification.
> Issue found with
> Coccinelle.
> 
> Signed-off-by: Nishka Dasgupta <nishkadg.linux@gmail.com>
> ---
>  drivers/auxdisplay/ht16k33.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/auxdisplay/ht16k33.c 
> b/drivers/auxdisplay/ht16k33.c
> index 9c0bb771751d..a2fcde582e2a 100644
> --- a/drivers/auxdisplay/ht16k33.c
> +++ b/drivers/auxdisplay/ht16k33.c
> @@ -74,7 +74,7 @@ struct ht16k33_priv {
>  	struct ht16k33_fbdev fbdev;
>  };
> 
> -static struct fb_fix_screeninfo ht16k33_fb_fix = {
> +static const struct fb_fix_screeninfo ht16k33_fb_fix = {
>  	.id		= DRIVER_NAME,
>  	.type		= FB_TYPE_PACKED_PIXELS,
>  	.visual		= FB_VISUAL_MONO10,
> @@ -85,7 +85,7 @@ static struct fb_fix_screeninfo ht16k33_fb_fix = {
>  	.accel		= FB_ACCEL_NONE,
>  };
> 
> -static struct fb_var_screeninfo ht16k33_fb_var = {
> +static const struct fb_var_screeninfo ht16k33_fb_var = {
>  	.xres = HT16K33_MATRIX_LED_MAX_ROWS,
>  	.yres = HT16K33_MATRIX_LED_MAX_COLS,
>  	.xres_virtual = HT16K33_MATRIX_LED_MAX_ROWS,

ACK

Robin

      parent reply	other threads:[~2019-08-20  6:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-19  7:51 Nishka Dasgupta
2019-08-19 16:48 ` Miguel Ojeda
2019-08-20  6:28 ` Robin van der Gracht [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=894371cda58112ee77cc0c8a5d336d2d@protonic.nl \
    --to=robin@protonic.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miguel.ojeda.sandonis@gmail.com \
    --cc=nishkadg.linux@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