All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@xilinx.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/3] bootstage: print all entries even if recorded time is zero
Date: Tue, 30 May 2017 14:22:12 +0200	[thread overview]
Message-ID: <2df2afb2f38b8b86a5035660ae7bf565f757dac1.1496146930.git.michal.simek@xilinx.com> (raw)
In-Reply-To: <0f47cf62b1af3dac5d2a1b9da65a4bf5364b6765.1496146930.git.michal.simek@xilinx.com>

From: Siva Durga Prasad Paladugu <siva.durga.paladugu@xilinx.com>

Print all entries in boot stage report even if the recorded
time stamp is zero. This lets the user to know all the recorded
entries that are made into. This helps user to know if something
went wrong with timestamp for that entry.

Signed-off-by: Siva Durga Prasad Paladugu <sivadur@xilinx.com>
Signed-off-by: Michal Simek <michal.simek@xilinx.com>
---

 common/bootstage.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/common/bootstage.c b/common/bootstage.c
index c8080dcab5d7..bca74cd207fc 100644
--- a/common/bootstage.c
+++ b/common/bootstage.c
@@ -277,7 +277,7 @@ void bootstage_report(void)
 	qsort(record, ARRAY_SIZE(record), sizeof(*rec), h_compare_record);
 
 	for (id = 0; id < BOOTSTAGE_ID_COUNT; id++, rec++) {
-		if (rec->time_us != 0 && !rec->start_us)
+		if ((rec->time_us != 0 && !rec->start_us) || rec->name)
 			prev = print_time_record(rec->id, rec, prev);
 	}
 	if (next_id > BOOTSTAGE_ID_COUNT)
-- 
1.9.1

  reply	other threads:[~2017-05-30 12:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-30 12:22 [U-Boot] [PATCH 1/3] bootstage: Dont print reset entry separately Michal Simek
2017-05-30 12:22 ` Michal Simek [this message]
2017-05-30 12:22 ` [U-Boot] [PATCH 3/3] bootstage: Modify routine timer_get_boot_us() Michal Simek
2017-06-09  1:00 ` [U-Boot] [U-Boot, 1/3] bootstage: Dont print reset entry separately Tom Rini
2017-06-21 10:51   ` Michal Simek

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=2df2afb2f38b8b86a5035660ae7bf565f757dac1.1496146930.git.michal.simek@xilinx.com \
    --to=michal.simek@xilinx.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 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.