From: Dan Carpenter <dan.carpenter@linaro.org>
To: "Ignacio Peña" <ignacio.pena87@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] staging: sm750fb: make fixId array static const char * const
Date: Sat, 19 Jul 2025 00:17:14 +0300 [thread overview]
Message-ID: <a9cd4eed-841a-4d00-aba3-5ffa0c40c3a7@suswa.mountain> (raw)
In-Reply-To: <aHq33vXh0F481FB-@MacBook-Pro-de-Ignacio.local>
On Fri, Jul 18, 2025 at 05:08:46PM -0400, Ignacio Peña wrote:
> Fix checkpatch warning for the fixId array only:
> "WARNING: static const char * array should probably be
> static const char * const"
>
> The g_fbmode array cannot be made const as it is modified at runtime
> in lynxfb_setup() and lynx_alloc().
>
> Signed-off-by: Ignacio Peña <ignacio.pena87@gmail.com>
> ---
> v4: Sorry for the confusion. Previous versions had wrong line numbers
> or included changes to g_fbmode. This version ONLY changes fixId
> at the correct line number (734) against current mainline.
Please stop sending new versions of the patch... At least wait a day
between sending new versions. This one was fine already.
No one cares about the line numbers. You had put that note about line
numbers under the --- cut off line so it's informational only and won't
be included in the final git log. Also line numbers are constantly
changing so we just ignore it when people tell us they are changing
line 123. It's not going to be line 123 on our end so it's not helpful.
regards,
dan carpenter
next prev parent reply other threads:[~2025-07-18 21:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-18 21:08 Ignacio Peña
2025-07-18 21:17 ` Dan Carpenter [this message]
2025-07-19 6:40 ` Greg Kroah-Hartman
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=a9cd4eed-841a-4d00-aba3-5ffa0c40c3a7@suswa.mountain \
--to=dan.carpenter@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=ignacio.pena87@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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
all inboxes | Powered by JetHome®