All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yordan Karadzhov (VMware)" <y.karadz@gmail.com>
To: rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org,
	"Yordan Karadzhov (VMware)" <y.karadz@gmail.com>
Subject: [PATCH v2] libtracefs: Fix code indentation
Date: Fri, 24 Sep 2021 17:57:20 +0300	[thread overview]
Message-ID: <20210924145720.164830-1-y.karadz@gmail.com> (raw)

This is a code style fix. No functional changes are introduced.

Signed-off-by: Yordan Karadzhov (VMware) <y.karadz@gmail.com>
---

I am re-sending this patch because the Tzvetomir reported problems
applying the previous version.

 include/tracefs.h  |  3 +--
 src/tracefs-hist.c | 12 ++++++------
 2 files changed, 7 insertions(+), 8 deletions(-)

diff --git a/include/tracefs.h b/include/tracefs.h
index 25abbdc..9d84777 100644
--- a/include/tracefs.h
+++ b/include/tracefs.h
@@ -309,8 +309,7 @@ enum tracefs_compare {
 	TRACEFS_COMPARE_AND,
 };
 
-void tracefs_hist_free
-(struct tracefs_hist *hist);
+void tracefs_hist_free(struct tracefs_hist *hist);
 struct tracefs_hist *
 tracefs_hist_alloc(struct tep_handle *tep,
 		   const char *system, const char *event,
diff --git a/src/tracefs-hist.c b/src/tracefs-hist.c
index 003715f..eeb8374 100644
--- a/src/tracefs-hist.c
+++ b/src/tracefs-hist.c
@@ -206,8 +206,8 @@ void tracefs_hist_free(struct tracefs_hist *hist)
  */
 struct tracefs_hist *
 tracefs_hist_alloc(struct tep_handle *tep,
-			const char *system, const char *event_name,
-			const char *key, enum tracefs_hist_key_type type)
+		   const char *system, const char *event_name,
+		   const char *key, enum tracefs_hist_key_type type)
 {
 	struct tep_event *event;
 	struct tracefs_hist *hist;
@@ -366,10 +366,10 @@ add_sort_key(struct tracefs_hist *hist, const char *sort_key, char **list)
 
 	if (!key_list[i]) {
 		for (i = 0; val_list[i]; i++) {
-		if (strcmp(val_list[i], sort_key) == 0)
-			break;
-		if (!val_list[i])
-			return NULL;
+			if (strcmp(val_list[i], sort_key) == 0)
+				break;
+			if (!val_list[i])
+				return NULL;
 		}
 	}
 
-- 
2.30.2


                 reply	other threads:[~2021-09-24 14:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20210924145720.164830-1-y.karadz@gmail.com \
    --to=y.karadz@gmail.com \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=rostedt@goodmis.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.