[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <00575D78-10FE-4A05-9BAB-5A2992AB401D@oracle.com>
Date: Thu, 17 Jan 2019 02:44:58 -0700
From: William Kucharski <william.kucharski@...cle.com>
To: Jane Chu <jane.chu@...cle.com>
Cc: Naoya Horiguchi <n-horiguchi@...jp.nec.com>,
Dan Williams <dan.j.williams@...el.com>,
Andrew Morton <akpm@...ux-foundation.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
linux-nvdimm <linux-nvdimm@...ts.01.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] mm: hwpoison: use do_send_sig_info() instead of
force_sig() (Re: PMEM error-handling forces SIGKILL causes kernel panic)
> On Jan 16, 2019, at 6:07 PM, Jane Chu <jane.chu@...cle.com> wrote:
>
> It's just coding style I'm used to, no big deal.
> Up to you to decide. :)
Personally I like a (void) cast as it's pretty long-standing syntactic sugar to cast a call that returns a value we don't care about to (void) to show we know it returns a value and we don't care.
Without it, it may suggest we either didn't know it returned a value or that we neglected to check the return value.
However, in current use elsewhere (e.g. in send_sig_all() and __oom_kill_process()), no such (void) cast is added, so it seems better to match current usage elsewhere in the kernel.
Reviewed-by: William Kucharski <william.kucharski@...cle.com>
Powered by blists - more mailing lists