All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot test failures; rebase on master
Date: Fri, 14 Dec 2018 17:53:03 +0100	[thread overview]
Message-ID: <f72f9a25-8a30-fbd7-98a0-410bea0d2f06@denx.de> (raw)
In-Reply-To: <ae637eb7-7517-7e1b-b5f4-e84e65356cd1@wwwdotorg.org>

On 12/14/2018 05:44 PM, Stephen Warren wrote:
> The following U-Boot repos have recently rebased on u-boot.git master
> branch, and picked up some changes that cause test failures on one/both
> of NVIDIA Jetson TX2 and sandbox. That potentially prevents any testing
> from finding any additional issues that are introduced in these repos.
> If you rebase on the latest u-boot.git master branch you'll pick up
> fixes that solve these failures, and make all of test/py pass on all the
> boards I test...
> 
> u-boot-usb.git master
> u-boot-video.git master
> u-boot-dfu.git master
> u-boot-spi.git master

Updated, thanks

-- 
Best regards,
Marek Vasut

  reply	other threads:[~2018-12-14 16:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-14 16:44 [U-Boot] U-Boot test failures; rebase on master Stephen Warren
2018-12-14 16:53 ` Marek Vasut [this message]
2018-12-14 18:53 ` Anatolij Gustschin

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=f72f9a25-8a30-fbd7-98a0-410bea0d2f06@denx.de \
    --to=marex@denx.de \
    --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.