From: Dan Carpenter <dan.carpenter@oracle.com>
To: alistair@popple.id.au
Cc: linuxppc-dev@lists.ozlabs.org
Subject: [bug report] powernv/opal: Convert opal message events to opal irq domain
Date: Tue, 14 Feb 2017 19:21:28 +0300 [thread overview]
Message-ID: <20170214162128.GA31029@mwanda> (raw)
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
reply other threads:[~2017-02-14 16:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20170214162128.GA31029@mwanda \
--to=dan.carpenter@oracle.com \
--cc=alistair@popple.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
/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.