From: Jingoo Han <jg1.han@samsung.com>
To: 'Tomasz Figa' <t.figa@samsung.com>,
'Cho KyongHo' <pullip.cho@samsung.com>
Cc: 'Linux DeviceTree' <devicetree@vger.kernel.org>,
'Linux Samsung SOC' <linux-samsung-soc@vger.kernel.org>,
'Prathyush' <prathyush.k@samsung.com>,
'Grant Grundler' <grundler@chromium.org>,
'Joerg Roedel' <joro@8bytes.org>,
'Jingoo Han' <jg1.han@samsung.com>,
'Linux Kernel' <linux-kernel@vger.kernel.org>,
'Sachin Kamat' <sachin.kamat@linaro.org>,
'Linux IOMMU' <iommu@lists.linux-foundation.org>,
'Kukjin Kim' <kgene.kim@samsung.com>,
'Sylwester Nawrocki' <s.nawrocki@samsung.com>,
'Varun Sethi' <Varun.Sethi@freescale.com>,
'Antonios Motakis' <a.motakis@virtualopensystems.com>,
'Linux ARM Kernel' <linux-arm-kernel@lists.infradead.org>,
'Rahul Sharma' <rahul.sharma@samsung.com>
Subject: Re: [PATCH v11 10/27] iommu/exynos: use managed device helper functions
Date: Wed, 19 Mar 2014 08:59:09 +0900 [thread overview]
Message-ID: <001201cf4306$0e16e540$2a44afc0$%han@samsung.com> (raw)
In-Reply-To: <5328625B.508@samsung.com>
On Wednesday, March 19, 2014 12:12 AM, Tomasz Figa wrote:
> On 18.03.2014 11:38, Cho KyongHo wrote:
> > On Fri, 14 Mar 2014 14:28:36 +0100, Tomasz Figa wrote:
> >> On 14.03.2014 06:05, Cho KyongHo wrote:
> >>> This patch uses managed device helper functions in the probe().
> >>>
> >>> Signed-off-by: Cho KyongHo <pullip.cho@samsung.com>
> >>> ---
> >>> drivers/iommu/exynos-iommu.c | 64 +++++++++++++++++-------------------------
> >>> 1 file changed, 26 insertions(+), 38 deletions(-)
> >>>
> >>> diff --git a/drivers/iommu/exynos-iommu.c b/drivers/iommu/exynos-iommu.c
> >>> index 36e6b73..33b424d 100644
> >>> --- a/drivers/iommu/exynos-iommu.c
> >>> +++ b/drivers/iommu/exynos-iommu.c
[.....]
> >>> res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
> >>> if (!res) {
> >>> - dev_dbg(dev, "Unable to find IOMEM region\n");
> >>> - ret = -ENOENT;
> >>> - goto err_init;
> >>> + dev_err(dev, "Unable to find IOMEM region\n");
> >>> + return -ENOENT;
> >>> }
> >>
> >> No need to check for error and print message, because
> >> devm_ioremap_resource() already checks the passed resource and handles
> >> error cases.
> >>
> >
> > Yes but devm_ioremap_resource() just tells that the given 'res' is not
> > correct. I think the message in the driver is more informative.
>
> The common practice used in Linux kernel is to not duplicate such
> messages. It is obvious that devm_ioremap_resource() printing such
> message is related to an IOMEM resource anyway, as you can't used it
> with other types of resources.
+1
I agree with Tomasz Figa's opinion.
These messages have been being removed from Linux kernel.
Thank you.
Best regards,
Jingoo Han
next prev parent reply other threads:[~2014-03-18 23:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-14 5:05 [PATCH v11 10/27] iommu/exynos: use managed device helper functions Cho KyongHo
[not found] ` <20140314140542.f4ded6c50dbd8a1d937bf354-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2014-03-14 13:28 ` Tomasz Figa
2014-03-18 10:38 ` Cho KyongHo
[not found] ` <20140318193817.3448387b75e109e814b9c025-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2014-03-18 15:12 ` Tomasz Figa
2014-03-18 23:59 ` Jingoo Han [this message]
[not found] ` <001201cf4306$0e16e540$2a44afc0$%han-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2014-03-19 8:56 ` Cho KyongHo
2014-03-14 15:22 ` Sachin Kamat
[not found] ` <CAK9yfHw7zYaX9EYFE+m3Mh-u8Uiyubx-cS0EwPmfW+0weLiBKw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-03-18 11:09 ` Cho KyongHo
2014-03-18 15:14 ` Tomasz Figa
[not found] ` <532862ED.8040809-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2014-03-19 8:59 ` Cho KyongHo
[not found] ` <20140319175927.a3feadcacbffe80eca1d3421-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2014-03-19 9:01 ` Sachin Kamat
2014-03-19 12:08 ` Tomasz Figa
[not found] ` <532988CA.4000008-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2014-03-20 10:03 ` Cho KyongHo
2014-03-20 10:44 ` Tomasz Figa
[not found] ` <532AC6A2.9070307-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-03-21 4:49 ` Cho KyongHo
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='001201cf4306$0e16e540$2a44afc0$%han@samsung.com' \
--to=jg1.han@samsung.com \
--cc=Varun.Sethi@freescale.com \
--cc=a.motakis@virtualopensystems.com \
--cc=devicetree@vger.kernel.org \
--cc=grundler@chromium.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=prathyush.k@samsung.com \
--cc=pullip.cho@samsung.com \
--cc=rahul.sharma@samsung.com \
--cc=s.nawrocki@samsung.com \
--cc=sachin.kamat@linaro.org \
--cc=t.figa@samsung.com \
/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).