From: Len Brown <len.brown@intel.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: akpm <akpm@osdl.org>,
linux-acpi@vger.kernel.org, viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH] acpi: cm_sbs: use NULL instead of 0 for ptr
Date: Tue, 26 Sep 2006 03:20:03 -0400 [thread overview]
Message-ID: <200609260320.03436.len.brown@intel.com> (raw)
In-Reply-To: <20060925214720.2f9778f9.rdunlap@xenotime.net>
Applied.
thanks,
-Len
On Tuesday 26 September 2006 00:47, Randy Dunlap wrote:
> From: Randy Dunlap <rdunlap@xenotime.net>
>
> Use NULL instead of 0 for pointer value, eliminate sparse warnings.
>
> Signed-off-by: Randy Dunlap <rdunlap@xenotime.net>
> ---
> drivers/acpi/cm_sbs.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> --- linux-2618-g4.orig/drivers/acpi/cm_sbs.c
> +++ linux-2618-g4/drivers/acpi/cm_sbs.c
> @@ -67,7 +67,7 @@ void acpi_unlock_ac_dir(struct proc_dir_
> lock_ac_dir_cnt--;
> if (lock_ac_dir_cnt == 0 && acpi_ac_dir_param && acpi_ac_dir) {
> remove_proc_entry(ACPI_AC_CLASS, acpi_root_dir);
> - acpi_ac_dir = 0;
> + acpi_ac_dir = NULL;
> }
> mutex_unlock(&cm_sbs_mutex);
> }
> @@ -99,7 +99,7 @@ void acpi_unlock_battery_dir(struct proc
> if (lock_battery_dir_cnt == 0 && acpi_battery_dir_param
> && acpi_battery_dir) {
> remove_proc_entry(ACPI_BATTERY_CLASS, acpi_root_dir);
> - acpi_battery_dir = 0;
> + acpi_battery_dir = NULL;
> }
> mutex_unlock(&cm_sbs_mutex);
> return;
>
>
> ---
> -
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2006-09-26 7:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 4:47 [PATCH] acpi: cm_sbs: use NULL instead of 0 for ptr Randy Dunlap
2006-09-26 7:20 ` Len Brown [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=200609260320.03436.len.brown@intel.com \
--to=len.brown@intel.com \
--cc=akpm@osdl.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=viro@zeniv.linux.org.uk \
/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.