From: Frank Rowand <frowand.list@gmail.com>
To: Moritz Fischer <moritz.fischer@ettus.com>, devicetree@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, robh+dt@kernel.org,
pantelis.antoniou@konsulko.com, mdf@kernel.org
Subject: Re: [PATCH v3 1/2] of: Fix issue where code would fall through to error case.
Date: Tue, 29 Nov 2016 10:41:24 -0800 [thread overview]
Message-ID: <583DCBD4.4010908@gmail.com> (raw)
In-Reply-To: <1480278058-19688-1-git-send-email-moritz.fischer@ettus.com>
On 11/27/16 12:20, Moritz Fischer wrote:
> No longer fall through into the error case that prints out
> an error if no error (err = 0) occurred.
>
> Rework error handling to print error where it occured instead
> of having a global catch-all at the end of the function.
>
> Fixes d9181b20a83(of: Add back an error message, restructured)
> Signed-off-by: Moritz Fischer <moritz.fischer@ettus.com>
> Reviewed-by: Frank Rowand <frank.rowand@am.sony.com>
> ---
> Hi Rob, Frank
>
> this has already Frank's Reviewed-by: tag on it, but since I changed around the
> earlier part (before tree_node gets assigned) Frank might wanna take another look
> at this.
< snip >
Hi Moritz,
I agree with Rob's suggested one line solution (that I initially misunderstood).
The one line fix is to add "if (err)" immediately following label "err_out" in
of_resolve_phandles().
As far as patch 2/2, I'm not bothered by the two instances of line over 80 chars.
But if Rob wants to take patch 2/2 I have no objection.
-Frank
prev parent reply other threads:[~2016-11-29 18:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-27 20:20 [PATCH v3 1/2] of: Fix issue where code would fall through to error case Moritz Fischer
2016-11-27 20:20 ` [PATCH v3 2/2] of: resolver: Fix checkpatch warnings Moritz Fischer
2016-11-29 18:41 ` Frank Rowand [this message]
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=583DCBD4.4010908@gmail.com \
--to=frowand.list@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@kernel.org \
--cc=moritz.fischer@ettus.com \
--cc=pantelis.antoniou@konsulko.com \
--cc=robh+dt@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).