From: Gary R Hook <gary.hook@amd.com>
To: "Gustavo A. R. Silva" <garsilva@embeddedor.com>,
"Lendacky, Thomas" <Thomas.Lendacky@amd.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>
Cc: "linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] crypto: ccp-platform: print error message on platform_get_irq failure
Date: Fri, 30 Jun 2017 10:08:00 -0500 [thread overview]
Message-ID: <cd383386-bdd1-c91a-09de-8c67d4503168@amd.com> (raw)
In-Reply-To: <20170630055952.GA6953@embeddedgus>
On 06/30/2017 12:59 AM, Gustavo A. R. Silva wrote:
> Print error message on platform_get_irq failure before return.
>
> Signed-off-by: Gustavo A. R. Silva <garsilva@embeddedor.com>
> ---
> drivers/crypto/ccp/ccp-platform.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/crypto/ccp/ccp-platform.c
> b/drivers/crypto/ccp/ccp-platform.c
> index e26969e..6020c4a 100644
> --- a/drivers/crypto/ccp/ccp-platform.c
> +++ b/drivers/crypto/ccp/ccp-platform.c
> @@ -66,8 +66,10 @@ static int ccp_get_irq(struct ccp_device *ccp)
> int ret;
>
> ret = platform_get_irq(pdev, 0);
> - if (ret < 0)
> + if (ret < 0) {
> + dev_notice(dev, "unable to get IRQ (%d)\n", ret);
> return ret;
> + }
Good find.
I'm all for better and more messages, but I'd like to see more detail
here, and in the
later dev_notice(). Can we have the messages better reflect the failure
points?
>
> ccp->irq = ret;
> ret = request_irq(ccp->irq, ccp->vdata->perform->irqhandler, 0,
> --
> 2.5.0
>
next prev parent reply other threads:[~2017-06-30 15:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-30 5:59 Gustavo A. R. Silva
2017-06-30 15:08 ` Gary R Hook [this message]
2017-07-18 10:36 ` Herbert Xu
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=cd383386-bdd1-c91a-09de-8c67d4503168@amd.com \
--to=gary.hook@amd.com \
--cc=Thomas.Lendacky@amd.com \
--cc=davem@davemloft.net \
--cc=garsilva@embeddedor.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®