From: Muli Ben-Yehuda <muli@il.ibm.com>
To: "Moore, Robert" <robert.moore@intel.com>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
Andrew Morton <akpm@osdl.org>, Len Brown <lenb@kernel.org>,
"Brown, Len" <len.brown@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ACPI List <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH] Cast removal
Date: Fri, 6 Oct 2006 16:35:55 +0200 [thread overview]
Message-ID: <20061006143555.GC14186@rhun.haifa.ibm.com> (raw)
In-Reply-To: <B28E9812BAF6E2498B7EC5C427F293A40114A6CB@orsmsx415.amr.corp.intel.com>
On Thu, Oct 05, 2006 at 03:14:02PM -0700, Moore, Robert wrote:
> If you're discussing this type of thing, I agree wholeheartedly:
>
> static void acpi_processor_notify(acpi_handle handle, u32 event, void
> *data) {
> - struct acpi_processor *pr = (struct acpi_processor *)data;
> + struct acpi_processor *pr = data;
>
>
> I find this one interesting, as we've put a number of them into the
> ACPICA core:
>
> - (void) kmem_cache_destroy(cache);
> + kmem_cache_destroy(cache);
>
> I believe that the point of the (void) is to prevent lint from
> squawking, and perhaps some picky ANSI-C compilers. What is the overall
> Linux policy on this?
IMHO there's another reason to do this which is much more relevant: it
tells the reader that whoever wrote it knows that it returns a value
and ignores it on purpose.
Cheers,
Muli
next prev parent reply other threads:[~2006-10-06 14:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-05 22:14 [PATCH] Cast removal Moore, Robert
2006-10-05 22:26 ` Andrew Morton
2006-10-06 5:34 ` Jan Engelhardt
2006-10-06 14:35 ` Muli Ben-Yehuda [this message]
2006-10-06 20:18 ` Jan Engelhardt
2006-10-06 20:30 ` Muli Ben-Yehuda
2006-10-06 20:39 ` Arjan van de Ven
-- strict thread matches above, loose matches on Subject: below --
2006-10-05 22:23 Brown, Len
2006-10-05 15:45 Moore, Robert
2006-10-04 21:40 Moore, Robert
2006-10-05 0:28 ` Andrew Morton
2006-09-30 22:28 Jan Engelhardt
2006-10-05 3:56 ` Len Brown
2006-10-05 4:12 ` Andrew Morton
2006-10-05 4:43 ` Len Brown
2006-10-05 5:19 ` Andrew Morton
2006-10-05 8:00 ` Jan Engelhardt
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=20061006143555.GC14186@rhun.haifa.ibm.com \
--to=muli@il.ibm.com \
--cc=akpm@osdl.org \
--cc=jengelh@linux01.gwdg.de \
--cc=len.brown@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robert.moore@intel.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