[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1281418597.1954.106.camel@Joe-Laptop.home>
Date: Mon, 09 Aug 2010 22:36:37 -0700
From: Joe Perches <joe@...ches.com>
To: stepanm@...eaurora.org
Cc: linux-arm-msm@...r.kernel.org, dwalker@...eaurora.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] arm: msm: Add MSM IOMMU support.
On Mon, 2010-08-09 at 20:42 -0700, stepanm@...eaurora.org wrote:
> I am actually considering doing away with all the pr_err lines entirely
> because they typically also result in returning -Ewhatever and other IOMMU
> drivers don't give this level of error reporting. But, they may be helpful
> to the users of the API. What are people's thoughts on this?
I believe the current uses of pr_err in this module
are unnecessary or could be converted to pr_debug.
I think __func__/line aren't particularly useful.
I prefer log messages prefixed with the module name.
#define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
and I'd convert all the current pr_err to pr_debug
and convert the printk(KERN_ERR to pr_err(
cheers, Joe
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists