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] [U-Boot, 1/3] bootstage: Dont print reset entry separately
Date: Wed, 21 Jun 2017 12:51:50 +0200	[thread overview]
Message-ID: <a9318009-fa88-b829-73d4-8572895a3e6c@xilinx.com> (raw)
In-Reply-To: <20170609010015.GA31908@bill-the-cat>

On 9.6.2017 03:00, Tom Rini wrote:
> On Tue, May 30, 2017 at 02:22:11PM +0200, Michal Simek wrote:
> 
>> From: Siva Durga Prasad Paladugu <siva.durga.paladugu@xilinx.com>
>>
>> Printing the first entry reset separately is no longer
>> needed as it now prints the entries with valid name and
>> timestamp zero. This removes duplicate printing of the reset
>> record.
>>
>> Signed-off-by: Siva Durga Prasad Paladugu <sivadur@xilinx.com>
>> Signed-off-by: Michal Simek <michal.simek@xilinx.com>
> 
> Can you please rebase this and the rest of the series on top of master
> again?  And please cc Simon when you repost, thanks!
> 

There are new patches from Simon. Siva will look at it and try to
validate them on our platforms.

Thanks,
Michal

      reply	other threads:[~2017-06-21 10:51 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 ` [U-Boot] [PATCH 2/3] bootstage: print all entries even if recorded time is zero Michal Simek
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 [this message]

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=a9318009-fa88-b829-73d4-8572895a3e6c@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.