From: Greg KH <gregkh@linuxfoundation.org>
To: Sanjana Sanikommu <sanjana99reddy99@gmail.com>
Cc: outreachy-kernel@googlegroups.com
Subject: Re: [PATCH] staging: greybus: svc_watchdog: Modify char* array declaration.
Date: Thu, 21 Mar 2019 19:58:14 +0100 [thread overview]
Message-ID: <20190321185814.GA17375@kroah.com> (raw)
In-Reply-To: <20190321073819.8333-1-sanjana99reddy99@gmail.com>
On Thu, Mar 21, 2019 at 01:08:19PM +0530, Sanjana Sanikommu wrote:
> Modify "static char* array" to "static char* const array".
> Issue found using checkpatch.pl
>
> WARNING:char* array declaration might be better as static constant
>
> Signed-off-by: Sanjana Sanikommu <sanjana99reddy99@gmail.com>
> ---
> drivers/staging/greybus/svc_watchdog.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/staging/greybus/svc_watchdog.c b/drivers/staging/greybus/svc_watchdog.c
> index 7868ad8211c5..b6aaabcec320 100644
> --- a/drivers/staging/greybus/svc_watchdog.c
> +++ b/drivers/staging/greybus/svc_watchdog.c
> @@ -44,12 +44,12 @@ static int svc_watchdog_pm_notifier(struct notifier_block *notifier,
> static void greybus_reset(struct work_struct *work)
> {
> static char const start_path[] = "/system/bin/start";
> - static char *envp[] = {
> + static char const *envp[] = {
> "HOME=/",
> "PATH=/sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin",
> NULL,
> };
> - static char *argv[] = {
> + static char const *argv[] = {
> (char *)start_path,
> "unipro_reset",
> NULL,
> --
> 2.17.1
>
Always test-build your patches before sending them out. You did not do
that here, why not? This blows up the build in horrible ways :(
greg k-h
prev parent reply other threads:[~2019-03-21 18:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 7:38 [PATCH] staging: greybus: svc_watchdog: Modify char* array declaration Sanjana Sanikommu
2019-03-21 18:58 ` Greg KH [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=20190321185814.GA17375@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=outreachy-kernel@googlegroups.com \
--cc=sanjana99reddy99@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.