* [bug report] powernv/opal: Convert opal message events to opal irq domain
@ 2017-02-14 16:21 Dan Carpenter
0 siblings, 0 replies; only message in thread
From: Dan Carpenter @ 2017-02-14 16:21 UTC (permalink / raw)
To: alistair; +Cc: linuxppc-dev
Hello Alistair Popple,
The patch a295af24d0d2: "powernv/opal: Convert opal message events to
opal irq domain" from May 15, 2015, leads to the following static
checker warning:
arch/powerpc/platforms/powernv/opal.c:297 opal_message_init()
info: return a literal instead of 'irq'
arch/powerpc/platforms/powernv/opal.c
286 static int __init opal_message_init(void)
287 {
288 int ret, i, irq;
289
290 for (i = 0; i < OPAL_MSG_TYPE_MAX; i++)
291 ATOMIC_INIT_NOTIFIER_HEAD(&opal_msg_notifier_head[i]);
292
293 irq = opal_event_request(ilog2(OPAL_EVENT_MSG_PENDING));
294 if (!irq) {
295 pr_err("%s: Can't register OPAL event irq (%d)\n",
296 __func__, irq);
297 return irq;
This code doesn't really make sense. I'm not really certain what it
should be...
298 }
299
300 ret = request_irq(irq, opal_message_notify,
301 IRQ_TYPE_LEVEL_HIGH, "opal-msg", NULL);
302 if (ret) {
303 pr_err("%s: Can't request OPAL event irq (%d)\n",
304 __func__, ret);
305 return ret;
306 }
307
308 return 0;
309 }
regards,
dan carpenter
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2017-02-14 16:22 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-02-14 16:21 [bug report] powernv/opal: Convert opal message events to opal irq domain Dan Carpenter
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).