public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] test/py: Detect timeout in phy negotiation
Date: Tue, 17 May 2016 10:50:07 -0600	[thread overview]
Message-ID: <573B4BBF.8090508@wwwdotorg.org> (raw)
In-Reply-To: <0abce825b8b0d541148207594be5bb1512cbf40e.1463493444.git.michal.simek@xilinx.com>

On 05/17/2016 07:57 AM, Michal Simek wrote:
> If timeout happen it should be reported as fault.

Presumably if a timeout occurs, the expected text does not appear, i.e. 
the existing assert fails anyway?

Anyway, it's useful to point out problems explicitly, so,
Acked-by: Stephen Warren <swarren@nvidia.com>

  reply	other threads:[~2016-05-17 16:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-17 13:57 [U-Boot] [PATCH] test/py: Detect timeout in phy negotiation Michal Simek
2016-05-17 16:50 ` Stephen Warren [this message]
2016-05-17 16:56   ` Michal Simek
2016-05-17 17:00     ` Stephen Warren
2016-05-17 17:03       ` Michal Simek
2016-05-17 17:36         ` Stephen Warren
2016-05-17 18:00           ` Michal Simek
2016-05-17 19:09             ` Stephen Warren
2016-05-18 10:56               ` 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=573B4BBF.8090508@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --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