public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: MottiKumar <mottikumarbabu@gmail.com>
Cc: linux-staging@lists.linux.dev, lkp@intel.com
Subject: Re: [PATCH v2] staging: sm750fb: fix const array warning for fix_id
Date: Tue, 6 Jan 2026 11:21:13 +0100	[thread overview]
Message-ID: <2026010630-exterior-body-2f46@gregkh> (raw)
In-Reply-To: <20251231084130.364502-1-mottikumarbabu@gmail.com>

On Wed, Dec 31, 2025 at 02:11:30PM +0530, MottiKumar wrote:
> This is version 2 of the patch. The previous version incorrectly
> modified the g_fbmode array, which caused a build failure because
> that array is modified at runtime.
> 
> This version leaves g_fbmode alone and instead applies the const
> fix to the fix_id array, which is a read-only lookup table.
> 
> Reported-by: kernel test robot <lkp@intel.com>

The kernel test robot did not report the original issue, only that your
first patch would not actually build, which implies you did not even do
that in your testing?

How was this version tested?

thanks,

greg k-h

      parent reply	other threads:[~2026-01-06 10:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-26 12:04 [PATCH] staging: sm750fb: fix const array warning MottiKumar
2025-12-30  7:42 ` Greg KH
     [not found]   ` <CAC9bbDKw-TGY81wecEnmhbMror0R=y8McTJGU5CPRf2N8UM9fQ@mail.gmail.com>
2025-12-30 12:51     ` Greg KH
2025-12-31  3:31 ` kernel test robot
2025-12-31  8:41   ` [PATCH v2] staging: sm750fb: fix const array warning for fix_id MottiKumar
2026-01-06 10:20     ` Greg Kroah-Hartman
2026-01-06 10:21     ` 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=2026010630-exterior-body-2f46@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=lkp@intel.com \
    --cc=mottikumarbabu@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