From: Moritz Fischer <moritz.fischer@ettus.com>
To: devicetree@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, frowand.list@gmail.com,
robh+dt@kernel.org, pantelis.antoniou@konsulko.com,
mdf@kernel.org, Moritz Fischer <moritz.fischer@ettus.com>
Subject: [PATCH v3 2/2] of: resolver: Fix checkpatch warnings
Date: Sun, 27 Nov 2016 12:20:58 -0800 [thread overview]
Message-ID: <1480278058-19688-2-git-send-email-moritz.fischer@ettus.com> (raw)
In-Reply-To: <1480278058-19688-1-git-send-email-moritz.fischer@ettus.com>
Fix two line over 80 character warnings that checkpatch spit out:
Before:
total: 0 errors, 2 warnings, 374 lines checked
drivers/of/resolver.c has style problems, please review.
After:
total: 0 errors, 0 warnings, 376 lines checked
Signed-off-by: Moritz Fischer <moritz.fischer@ettus.com>
---
Hi,
this one just silences two checkpatch warnings that I ran
into when running checkpatch against my patches.
There's a bunch of 'CHECK' level things in this file that
I could address in a follow up patch if desired.
Cheers,
Moritz
---
drivers/of/resolver.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/of/resolver.c b/drivers/of/resolver.c
index 5f51a4a..71f98dc 100644
--- a/drivers/of/resolver.c
+++ b/drivers/of/resolver.c
@@ -311,7 +311,8 @@ int of_resolve_phandles(struct device_node *overlay)
if (!of_node_cmp(local_fixups->name, "__local_fixups__"))
break;
- err = adjust_local_phandle_references(local_fixups, overlay, phandle_delta);
+ err = adjust_local_phandle_references(local_fixups, overlay,
+ phandle_delta);
if (err) {
pr_err("overlay phandle fixup failed: %d\n", err);
return err;
@@ -356,7 +357,8 @@ int of_resolve_phandles(struct device_node *overlay)
phandle = refnode->phandle;
of_node_put(refnode);
- err = update_usages_of_a_phandle_reference(overlay, prop, phandle);
+ err = update_usages_of_a_phandle_reference(overlay, prop,
+ phandle);
if (err)
break;
}
--
2.7.4
next prev parent reply other threads:[~2016-11-27 20:21 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 ` Moritz Fischer [this message]
2016-11-29 18:41 ` Frank Rowand
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=1480278058-19688-2-git-send-email-moritz.fischer@ettus.com \
--to=moritz.fischer@ettus.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@kernel.org \
--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
all inboxes | Powered by JetHome®