From: Julia Lawall <julia.lawall@lip6.fr>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Harsha Sharma <harshasharmaiitr@gmail.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] Re: [PATCH] staging: unisys: visorbus: Declared char * array as static const
Date: Sat, 9 Sep 2017 10:36:08 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1709091034170.2025@hadrien> (raw)
In-Reply-To: <20170909071451.GA27010@kroah.com>
On Sat, 9 Sep 2017, Greg KH wrote:
> On Sat, Sep 09, 2017 at 12:30:42PM +0530, Harsha Sharma wrote:
> > State explicitly that individual entries in array will not change.
> >
> > Signed-off-by: Harsha Sharma <harshasharmaiitr@gmail.com>
> > ---
> > drivers/staging/unisys/visorbus/visorchipset.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/staging/unisys/visorbus/visorchipset.c b/drivers/staging/unisys/visorbus/visorchipset.c
> > index 6d4498f..6f2a010 100644
> > --- a/drivers/staging/unisys/visorbus/visorchipset.c
> > +++ b/drivers/staging/unisys/visorbus/visorchipset.c
> > @@ -1162,7 +1162,7 @@ static ssize_t deviceenabled_store(struct device *dev,
> > struct controlvm_message_packet *cmd = &req->msg.cmd;
> > char env_cmd[40], env_id[40], env_state[40], env_bus[40], env_dev[40],
> > env_func[40];
> > - char *envp[] = {
> > + static const char * const envp[] = {
>
> Are you _sure_ about this? Why make it static? That seems a bit "odd",
> don't you think? You need a lot more changelog text to get everyone to
> agree that this is ok to do...
Harsha,
Study carefully what static means when it is attached to a local variable.
And be sure that your code actually compiles. If it doesn't try to figure
out why not. There are other commits that are sort of like this on in the
kernel that you can find using git log. But you may notice that they are
different in some way from yours.
julia
>
> Also, you forgot to cc: the actual maintainers of this code...
>
> thanks,
>
> greg k-h
>
> --
> You received this message because you are subscribed to the Google Groups "outreachy-kernel" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to outreachy-kernel+unsubscribe@googlegroups.com.
> To post to this group, send email to outreachy-kernel@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/outreachy-kernel/20170909071451.GA27010%40kroah.com.
> For more options, visit https://groups.google.com/d/optout.
>
next prev parent reply other threads:[~2017-09-09 8:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-09 7:00 Harsha Sharma
2017-09-09 7:14 ` Greg KH
2017-09-09 8:36 ` Julia Lawall [this message]
2017-09-11 9:30 ` kbuild test robot
2017-09-12 0:29 ` kbuild test robot
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=alpine.DEB.2.20.1709091034170.2025@hadrien \
--to=julia.lawall@lip6.fr \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=harshasharmaiitr@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=outreachy-kernel@googlegroups.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
all inboxes | Powered by JetHome®