All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ethan Edwards <ethancarteredwards@gmail.com>
To: clm@fb.com
Cc: linux-kernel@vger.kernel.org, linux-btrfs@vger.kernel.org,
	Ethan Edwards <ethancarteredwards@gmail.com>
Subject: [PATCH] FS: BTRFS: ulist.c: Fixed a brace coding style and space before tab
Date: Fri, 22 May 2020 17:29:02 -0400	[thread overview]
Message-ID: <20200522212902.20994-1-ethancarteredwards@gmail.com> (raw)

From: Ethan Edwards <ethancarteredwards@gmail.com

Fixed coding style

Signed-off-by: Ethan Edwards <ethancarteredwards@gmail.com>
---
 fs/btrfs/ulist.c | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/fs/btrfs/ulist.c b/fs/btrfs/ulist.c
index 3374c9e9be67..1e0484c8d244 100644
--- a/fs/btrfs/ulist.c
+++ b/fs/btrfs/ulist.c
@@ -22,7 +22,7 @@
  * ULIST_ITER_INIT(&uiter);
  *
  * while ((elem = ulist_next(ulist, &uiter)) {
- * 	for (all child nodes n in elem)
+ *	for (all child nodes n in elem)
  *		ulist_add(ulist, n);
  *	do something useful with the node;
  * }
@@ -266,11 +266,11 @@ struct ulist_node *ulist_next(struct ulist *ulist, struct ulist_iterator *uiter)
 		return NULL;
 	if (uiter->cur_list && uiter->cur_list->next == &ulist->nodes)
 		return NULL;
-	if (uiter->cur_list) {
+	if (uiter->cur_list)
 		uiter->cur_list = uiter->cur_list->next;
-	} else {
+	else
 		uiter->cur_list = ulist->nodes.next;
-	}
+
 	node = list_entry(uiter->cur_list, struct ulist_node, list);
 	return node;
 }
-- 
2.26.2


             reply	other threads:[~2020-05-22 21:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-22 21:29 Ethan Edwards [this message]
2020-05-25 12:37 ` [PATCH] FS: BTRFS: ulist.c: Fixed a brace coding style and space before tab David Sterba

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=20200522212902.20994-1-ethancarteredwards@gmail.com \
    --to=ethancarteredwards@gmail.com \
    --cc=clm@fb.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.