From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Valentin Rothberg <valentin.rothberg@posteo.net>, ldewangan@nvidia.com
Cc: kbuild-all@01.org, alexandre.belloni@free-electrons.com,
javier@osg.samsung.com, cw00.choi@samsung.com,
a.zummo@towertech.it, linux-kernel@vger.kernel.org,
rtc-linux@googlegroups.com,
kbuild test robot <fengguang.wu@intel.com>
Subject: [rtc-linux] Re: [PATCH] rtc: max77686: fix irqf_oneshot.cocci warnings
Date: Thu, 18 Feb 2016 17:13:18 +0900 [thread overview]
Message-ID: <56C57D1E.805@samsung.com> (raw)
In-Reply-To: <1455782816-5814-1-git-send-email-valentin.rothberg@posteo.net>
On 18.02.2016 17:06, Valentin Rothberg wrote:
> From: kbuild test robot <fengguang.wu@intel.com>
>
> Since commit 1c6c69525b40 ("genirq: Reject bogus threaded irq requests")
> threaded IRQs without a primary handler need to be requested with
> IRQF_ONESHOT, otherwise the request will fail.
>
> So pass the IRQF_ONESHOT flag in this case.
>
> Generated by: scripts/coccinelle/misc/irqf_oneshot.cocci
>
> CC: Laxman Dewangan <ldewangan@nvidia.com>
> Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
> Signed-off-by: Valentin Rothberg <valentin.rothberg@posteo.net>
> ---
> drivers/rtc/rtc-max77686.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
Nack, because:
1. AFAIR this is a false positive.
2. Was it tested? Was it reproduced? Was the bug actually spotted or
just coccicheck pointed this and you assumed that "request will fail"?
Coccicheck is a great tool... but not necessarily for pointing run-time
bugs.
Best regards,
Krzysztof
--
--
You received this message because you are subscribed to "rtc-linux".
Membership options at http://groups.google.com/group/rtc-linux .
Please read http://groups.google.com/group/rtc-linux/web/checklist
before submitting a driver.
---
You received this message because you are subscribed to the Google Groups "rtc-linux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rtc-linux+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
next prev parent reply other threads:[~2016-02-18 8:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 8:06 [rtc-linux] [PATCH] rtc: max77686: fix irqf_oneshot.cocci warnings Valentin Rothberg
2016-02-18 8:13 ` Krzysztof Kozlowski [this message]
2016-02-18 8:46 ` [rtc-linux] " Valentin Rothberg
2016-02-18 8:50 ` Krzysztof Kozlowski
2016-02-18 9:03 ` Valentin Rothberg
2016-02-18 8:51 ` Alexandre Belloni
2016-02-18 9:23 ` Valentin Rothberg
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=56C57D1E.805@samsung.com \
--to=k.kozlowski@samsung.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@free-electrons.com \
--cc=cw00.choi@samsung.com \
--cc=fengguang.wu@intel.com \
--cc=javier@osg.samsung.com \
--cc=kbuild-all@01.org \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rtc-linux@googlegroups.com \
--cc=valentin.rothberg@posteo.net \
/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