All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Otavio Salvador" <otavio.salvador@ossystems.com.br>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: OpenEmbedded Core Mailing List
	<openembedded-core@lists.openembedded.org>,
	 Stefano Babic <sbabic@denx.de>, Tom Rini <trini@konsulko.com>,
	 Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: [OE-core] [PATCH v2] u-boot: Restore valid default environment for running system
Date: Wed, 1 Apr 2020 10:17:47 -0300	[thread overview]
Message-ID: <CAP9ODKpuLkYW07JV-+8bE_V4nKEGjnKUvuE3yrw9nJBY3RJc3g@mail.gmail.com> (raw)
In-Reply-To: <6e0af711c659eeb8fdb223a1fd58d907fe73b90d.camel@linuxfoundation.org>

On Wed, Apr 1, 2020 at 6:24 AM Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
...
> Sadly it breaks oe-selftest's sstatetests:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/825
>
> (reproduce with oe-selftest -r sstatetests.SStateTests)
>
> As well as world build file conflicts in deploy:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/108/builds/405
> https://autobuilder.yoctoproject.org/typhoon/#/builders/52/builds/1731
>
> which is a large number of issues to introduce just before final
> release :(

Sure; these errors are not acceptable. I am checking it right away.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9 9981-7854          Mobile: +1 (347) 903-9750

      reply	other threads:[~2020-04-01 13:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-31 15:16 [PATCH v2] u-boot: Restore valid default environment for running system Otavio Salvador
2020-03-31 15:32 ` Stefano Babic
2020-03-31 16:44   ` [OE-core] " Otavio Salvador
2020-03-31 17:03     ` Stefano Babic
2020-03-31 17:52       ` Otavio Salvador
2020-04-01  9:38   ` Ayoub Zaki
2020-04-01  9:24 ` Richard Purdie
2020-04-01 13:17   ` Otavio Salvador [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=CAP9ODKpuLkYW07JV-+8bE_V4nKEGjnKUvuE3yrw9nJBY3RJc3g@mail.gmail.com \
    --to=otavio.salvador@ossystems.com.br \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=sbabic@denx.de \
    --cc=trini@konsulko.com \
    /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.