From: peter.ujfalusi@ti.com (Peter Ujfalusi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 5/5] drivers: bus: omap_l3: Change pr_crit() to dev_err() when IRQ request fails
Date: Wed, 5 Mar 2014 09:11:19 +0200 [thread overview]
Message-ID: <5316CE17.6010201@ti.com> (raw)
In-Reply-To: <5315E522.9090606@ti.com>
On 03/04/2014 04:37 PM, Santosh Shilimkar wrote:
> On Tuesday 04 March 2014 08:48 PM, Peter Ujfalusi wrote:
>> Use dev_err() which will going to print the driver's name as well and the
>> KERN_ERR level is sufficient in this case (we also print via dev_err when
>> there is an error with the mem resources)
>>
>> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
>> Reviewed-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
>> ---
>> drivers/bus/omap_l3_noc.c | 7 +++----
>> 1 file changed, 3 insertions(+), 4 deletions(-)
>>
>> diff --git a/drivers/bus/omap_l3_noc.c b/drivers/bus/omap_l3_noc.c
>> index 0eff48585ae3..972691a668a3 100644
>> --- a/drivers/bus/omap_l3_noc.c
>> +++ b/drivers/bus/omap_l3_noc.c
>> @@ -158,8 +158,8 @@ static int omap4_l3_probe(struct platform_device *pdev)
>> ret = devm_request_irq(&pdev->dev, l3->debug_irq, l3_interrupt_handler,
>> IRQF_DISABLED, "l3-dbg-irq", l3);
>> if (ret) {
>> - pr_crit("L3: request_irq failed to register for 0x%x\n",
>> - l3->debug_irq);
>> + dev_err(&pdev->dev, "request_irq failed for %d\n",
>> + l3->debug_irq);
>> return ret;
>> }
>>
>> @@ -167,8 +167,7 @@ static int omap4_l3_probe(struct platform_device *pdev)
>> ret = devm_request_irq(&pdev->dev, l3->app_irq, l3_interrupt_handler,
>> IRQF_DISABLED, "l3-app-irq", l3);
>> if (ret)
>> - pr_crit("L3: request_irq failed to register for 0x%x\n",
>> - l3->app_irq);
>> + dev_err(&pdev->dev, "request_irq failed for %d\n", l3->app_irq);
>>
>> return ret;
>> }
>>
> So this one change in the log level. If I look at now, may be dev_err
> is fine but the change is not same.
Not sure what you mean by 'the change is not same'?
I just picked the old series and rebased it on linux-next, the patch is the
same as it was back in May 2013:
https://lkml.org/lkml/2013/5/2/205
And yes, I have shortened the texts in the print, but the meaning of the
prints have not changed.
> Apart from above comment, rest of the series looks fine to me.
> Feel free to add my ack...
Thanks.
--
P?ter
next prev parent reply other threads:[~2014-03-05 7:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-04 12:48 [PATCH v3 0/5] drivers: bus: omap_l3: Conversion to devm_* Peter Ujfalusi
2014-03-04 12:48 ` [PATCH v3 1/5] drivers: bus: omap_l3: Convert to use devm_kzalloc Peter Ujfalusi
2014-03-04 12:48 ` [PATCH v3 2/5] drivers: bus: omap_l3: Convert to use devm_ioremap_resource() Peter Ujfalusi
2014-03-04 12:48 ` [PATCH v3 3/5] drivers: bus: omap_l3: Convert to use devm_request_irq() Peter Ujfalusi
2014-03-04 12:48 ` [PATCH v3 4/5] drivers: bus: omap_l3: Remove the platform driver's remove function Peter Ujfalusi
2014-03-04 12:48 ` [PATCH v3 5/5] drivers: bus: omap_l3: Change pr_crit() to dev_err() when IRQ request fails Peter Ujfalusi
2014-03-04 14:37 ` Santosh Shilimkar
2014-03-05 7:11 ` Peter Ujfalusi [this message]
2014-03-12 17:28 ` Tony Lindgren
2014-03-12 21:05 ` Santosh Shilimkar
2014-03-12 21:11 ` Tony Lindgren
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=5316CE17.6010201@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).