From: Walt Feasel <waltfeasel@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-BOOT][TEST PATCH 2/5] Cosmetic api: api_storage.c Blank line after {
Date: Wed, 23 Nov 2016 01:26:11 -0500 [thread overview]
Message-ID: <1479882374-18434-3-git-send-email-waltfeasel@gmail.com> (raw)
In-Reply-To: <1479882374-18434-1-git-send-email-waltfeasel@gmail.com>
Make checkpatch style modification for
CHECK: Blank lines aren't necessary after
an open brace '{'
Signed-off-by: Walt Feasel <waltfeasel@gmail.com>
---
This patch series is to verify a correct patch submission.
Please let me know if there is a problem or preferred
wording for submitting cosmetic patches.
api/api_storage.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/api/api_storage.c b/api/api_storage.c
index ea44d97..9c4ff5b 100644
--- a/api/api_storage.c
+++ b/api/api_storage.c
@@ -220,7 +220,6 @@ static int dev_enum_stor(int type, struct device_info *di)
*/
if (di->cookie == NULL) {
-
debugf("group%d - enum restart\n", type);
/*
@@ -231,7 +230,6 @@ static int dev_enum_stor(int type, struct device_info *di)
specs[type].enum_started = 1;
} else if (dev_is_stor(type, di)) {
-
debugf("group%d - enum continued for the next device\n", type);
if (specs[type].enum_ended) {
@@ -243,7 +241,6 @@ static int dev_enum_stor(int type, struct device_info *di)
found = dev_stor_get(type, 0, &more, di);
} else {
-
if (specs[type].enum_ended) {
debugf("group %d - already enumerated, skipping\n", type);
return 0;
--
2.1.4
next prev parent reply other threads:[~2016-11-23 6:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 6:26 [U-Boot] [U-BOOT][TEST PATCH 0/5] Cosmetic modifications api_storage.c Walt Feasel
2016-11-23 6:26 ` [U-Boot] [U-BOOT][TEST PATCH 1/5] Cosmetic api: api_storage.c Align parenthesis Walt Feasel
2016-12-04 23:14 ` [U-Boot] [U-Boot, U-BOOT, TEST, " Tom Rini
2016-11-23 6:26 ` Walt Feasel [this message]
2016-12-04 23:15 ` [U-Boot] [U-Boot, U-BOOT, TEST, 2/5] Cosmetic api: api_storage.c Blank line after { Tom Rini
2016-11-23 6:26 ` [U-Boot] [U-BOOT][TEST PATCH 3/5] Cosmetic api: api_storage.c Line over 80 char Walt Feasel
2016-12-04 23:15 ` [U-Boot] [U-Boot, U-BOOT, TEST, " Tom Rini
2016-11-23 6:26 ` [U-Boot] [U-BOOT][TEST PATCH 4/5] Cosmetic api: api_storage.c Comment style Walt Feasel
2016-12-04 23:16 ` [U-Boot] [U-Boot, U-BOOT, TEST, " Tom Rini
2016-11-23 6:26 ` [U-Boot] [U-BOOT][TEST PATCH 5/5] Cosmetic api: api_storage.c Spelling correction Walt Feasel
2016-12-04 23:16 ` [U-Boot] [U-Boot, U-BOOT, TEST, " Tom Rini
2016-11-23 14:03 ` [U-Boot] [U-BOOT][TEST PATCH 0/5] Cosmetic modifications api_storage.c Walt Feasel
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=1479882374-18434-3-git-send-email-waltfeasel@gmail.com \
--to=waltfeasel@gmail.com \
--cc=u-boot@lists.denx.de \
/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