From: Frank Rowand <frowand.list@gmail.com>
To: Rob Herring <robh@kernel.org>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Pantelis Antoniou <pantelis.antoniou@konsulko.com>
Subject: Re: [PATCH] of: use pr_fmt prefix for all console printing
Date: Thu, 2 Jun 2016 14:44:16 -0700 [thread overview]
Message-ID: <5750A8B0.9010702@gmail.com> (raw)
In-Reply-To: <CAL_JsqLrC27EOkWfRtzUOZox5wkRU=qEb+b3z2JQG++e5uSGSg@mail.gmail.com>
On 06/02/16 12:56, Rob Herring wrote:
> On Thu, Jun 2, 2016 at 12:33 PM, Frank Rowand <frowand.list@gmail.com> wrote:
>> On 06/02/16 08:14, Rob Herring wrote:
>>> Clean-up all the DT printk functions to use common pr_fmt prefix.
>>>
>>> Some print statements such as kmalloc errors were redundant, so just
>>> drop those.
>>>
>>> Cc: Frank Rowand <frowand.list@gmail.com>
>>> Cc: Pantelis Antoniou <pantelis.antoniou@konsulko.com>
>>> Signed-off-by: Rob Herring <robh@kernel.org>
>>> ---
>>> drivers/of/address.c | 49 ++++++++++++++++++++++----------------------
>>> drivers/of/base.c | 11 ++++++----
>>> drivers/of/dynamic.c | 47 +++++++++++++++++++++---------------------
>>> drivers/of/fdt.c | 12 +++++------
>>> drivers/of/fdt_address.c | 35 ++++++++++++++++---------------
>>> drivers/of/irq.c | 2 ++
>>> drivers/of/of_numa.c | 22 ++++++--------------
>>> drivers/of/of_pci.c | 6 ++++--
>>> drivers/of/of_reserved_mem.c | 22 ++++++++++----------
>>> drivers/of/overlay.c | 43 +++++++++++++++-----------------------
>>> drivers/of/platform.c | 16 +++++++--------
>>> drivers/of/resolver.c | 2 ++
>>> 12 files changed, 130 insertions(+), 137 deletions(-)
>>>
>>
>> Nice cleanup. A couple of comments below.
>>
>> Reviewed-by: Frank Rowand <frank.rowand@am.sony.com>
>>
>> < snip >
< snip >
>>> @@ -355,8 +355,6 @@ int of_overlay_create(struct device_node *tree)
>>>
>>> id = idr_alloc(&ov_idr, ov, 0, 0, GFP_KERNEL);
>>> if (id < 0) {
>>> - pr_err("%s: idr_alloc() failed for tree@%s\n",
>>> - __func__, tree->full_name);
>>
>> Every other error in of_overlay_create() results in a pr_err().
>> (The other cases of removing pr_err() in this file are fine, because
>> the errors are already reported in the functions called from this
>> function.)
>>
>> I would recommend leaving in the pr_err() for idr_alloc() failure.
>
> I was thinking idr_alloc is going to call kmalloc which will print
> errors on failure, but there may be some case it doesn't.
>
> Rob
I did not read idr_alloc() carefully enough. Given the arguments it
is called with, none of the non-kmalloc error returns are possible.
So you were correct to remove this pr_err().
-Frank
next prev parent reply other threads:[~2016-06-02 21:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 15:14 [PATCH] of: use pr_fmt prefix for all console printing Rob Herring
[not found] ` <1464880499-29864-1-git-send-email-robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2016-06-02 17:33 ` Frank Rowand
2016-06-02 19:56 ` Rob Herring
2016-06-02 20:10 ` Joe Perches
2016-06-02 21:44 ` Frank Rowand [this message]
2016-06-03 7:54 ` kbuild test robot
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=5750A8B0.9010702@gmail.com \
--to=frowand.list@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pantelis.antoniou@konsulko.com \
--cc=robh@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;
as well as URLs for NNTP newsgroup(s).