linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Hariprasad Kelam <hariprasad.kelam@gmail.com>,
	Wim Van Sebroeck <wim@linux-watchdog.org>,
	linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] watchdog: machzwd : fix warning Using plain integer as NULL pointer
Date: Sat, 6 Apr 2019 12:32:53 -0700	[thread overview]
Message-ID: <3d381fb9-4721-d2a9-9829-56697afd727c@roeck-us.net> (raw)
In-Reply-To: <20190406131415.GA3844@hari-Inspiron-1545>

On 4/6/19 6:14 AM, Hariprasad Kelam wrote:
> Changes passing function argument 0 to NULL to avoid below sparse
> warning
> 
>   CHECK   drivers/watchdog//machzwd.c
> drivers/watchdog//machzwd.c:321:25: warning: Using plain integer as NULL
> pointer
> 
> Signed-off-by: Hariprasad Kelam <hariprasad.kelam@gmail.com>

[reluctantly]

Reviewed-by: Guenter Roeck <linux@roeck-us.net>

If anyone is still using the HW supported by this driver, it would
be a prime target for conversion to use the watchdog subsystem.
This would reduce code size and improve driver stability.
_That_ would be useful.

The only reason for replacing 0 with NULL is to make a static checker
happy. This kind of change adds zero value to the code. Instead, it
takes time from those who have to review the patches and apply them.

If we ignore such patches, we'll get them again and again, taking
away even more time. If we don't ignore them, we encourage submitters
and get even more useless patches. If we try to discourage them, we
risk being accused of being unfriendly. This is a perfect lose-lose
situation for maintainers.

Guenter

> ---
>   drivers/watchdog/machzwd.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/watchdog/machzwd.c b/drivers/watchdog/machzwd.c
> index 88d823d..c3926d0 100644
> --- a/drivers/watchdog/machzwd.c
> +++ b/drivers/watchdog/machzwd.c
> @@ -318,7 +318,7 @@ static long zf_ioctl(struct file *file, unsigned int cmd, unsigned long arg)
>   	case WDIOC_GETBOOTSTATUS:
>   		return put_user(0, p);
>   	case WDIOC_KEEPALIVE:
> -		zf_ping(0);
> +		zf_ping(NULL);
>   		break;
>   	default:
>   		return -ENOTTY;
> 


      parent reply	other threads:[~2019-04-06 19:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-06 13:14 [PATCH] watchdog: machzwd : fix warning Using plain integer as NULL pointer Hariprasad Kelam
2019-04-06 18:47 ` Mukesh Ojha
2019-04-06 19:32 ` Guenter Roeck [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=3d381fb9-4721-d2a9-9829-56697afd727c@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=hariprasad.kelam@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=wim@linux-watchdog.org \
    /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;
as well as URLs for NNTP newsgroup(s).