From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: sudipm.mukherjee@gmail.com, gregkh@linuxfoundation.org,
outreachy-kernel@googlegroups.com, kushalkothari2850@gmail.com
Cc: teddy.wang@siliconmotion.com, mike.rapoport@gmail.com,
Kushal Kothari <kushalkothari285@gmail.com>,
Kushal Kothari <kushalkothari285@gmail.com>,
linux-staging@lists.linux.dev,
Karolina Drobnik <karolinadrobnik@gmail.com>,
julia.lawall@inria.fr
Subject: Re: [Outreachy kernel] [PATCH] staging: sm750fb: make pointers in array const
Date: Mon, 18 Oct 2021 20:18:53 +0200 [thread overview]
Message-ID: <2371688.97nOaecjje@localhost.localdomain> (raw)
In-Reply-To: <163460335.XzdQGyDEVH@localhost.localdomain>
On Monday, October 18, 2021 6:54:34 PM CEST Fabio M. De Francesco wrote:
> On Monday, October 18, 2021 6:44:31 PM CEST Kushal Kothari wrote:
> > Change the parameters of functions from const char *g_fbmode[] to
> > const char * const g_fbmode[]. This additional const is needed to
> > allow us to fix checkpatch warning, as well as being good
> > programming practice.
> >
> > For the checkpatch warnings, if we have a set of command line
> > args that we want to check defined as:
> > static const char * g_fbmode[] = {NULL, NULL};
> >
> > checkpatch will complain:
> > WARNING: static const char * array should probably be static
const
> char * const
> >
> > Signed-off-by: Kushal Kothari <kushalkothari285@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 dbd1159a2ef0..3d9b4b0efcb1 100644
> > --- a/drivers/staging/sm750fb/sm750.c
> > +++ b/drivers/staging/sm750fb/sm750.c
> > @@ -33,7 +33,7 @@
> > static int g_hwcursor = 1;
> > static int g_noaccel;
> > static int g_nomtrr;
> > -static const char *g_fbmode[] = {NULL, NULL};
> > +static const char * const g_fbmode[] = {NULL, NULL};
>
> You have introduced a logical change (g_fbmode[] entries cannot be assigned
> any more) and a build error (because there is code somewhere that assigns
> values to those slots).
>
> Please, build the code after you've changed it.
>
> Thanks,
>
> Fabio
Hi Kushal,
As I wrote your patch has errors, however, if it had no errors it could not
be taken in any case. I just noticed that you forgot to CC linux-
staging@lists.linux.dev.
Some days ago, Greg Kroah-Hartman wrote clearly that he cannot take patches
that are not submitted to linux-staging.
The "Submit patches" section of https://kernelnewbies.org/Outreachyfirstpatch
is a bit misleading. However, Karolina Drobnik is taking care to rework it.
For the moment, please use the following command (or some smart variation of
it) to get a list with _all_ the people and mailing lists you should send
your patches to:
kernel_source_dir@localhost:~ # perl scripts/get_maintainer.pl --separator ,
--norolestats -f drivers/staging/sm750fb/
The output is:
Sudip Mukherjee <sudipm.mukherjee@gmail.com>,Teddy Wang
<teddy.wang@siliconmotion.com>,Greg Kroah-Hartman
<gregkh@linuxfoundation.org>,linux-fbdev@vger.kernel.org,linux-
staging@lists.linux.dev,linux-kernel@vger.kernel.org
Thanks,
Fabio
P.S.: @Karolina, please correct me if I wrote something that is wrong and
that contradicts the new text you are working on.
parent reply other threads:[~2021-10-18 18:18 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <163460335.XzdQGyDEVH@localhost.localdomain>]
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=2371688.97nOaecjje@localhost.localdomain \
--to=fmdefrancesco@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=julia.lawall@inria.fr \
--cc=karolinadrobnik@gmail.com \
--cc=kushalkothari2850@gmail.com \
--cc=kushalkothari285@gmail.com \
--cc=linux-staging@lists.linux.dev \
--cc=mike.rapoport@gmail.com \
--cc=outreachy-kernel@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox