openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Lei Yu <yulei.sh@bytedance.com>
To: Patrick Williams <patrick@stwcx.xyz>
Cc: OpenBMC List <openbmc@lists.ozlabs.org>
Subject: Re: [External] Re: Yocto override syntax change.
Date: Fri, 13 Aug 2021 11:19:31 +0800	[thread overview]
Message-ID: <CAGm54UHNeYu9vEcL8R98UMn8qEsSQ6yNK3PUX_dzixzh2n_9gA@mail.gmail.com> (raw)
In-Reply-To: <YRUW7cazmCjW8VpP@heinlein>

On Thu, Aug 12, 2021 at 8:41 PM Patrick Williams <patrick@stwcx.xyz> wrote:
>
> On Fri, Aug 06, 2021 at 09:19:59AM -0500, Patrick Williams wrote:
>
> > TL;DR: There is a required change to all meta-layers by Wednesday August 11,
> > 2021 at 1PM UTC.  Any meta-layer not changed by that time may no longer compile.
>
> This change is now merged into our branch.  All of our machines listed in CI
> are able to build successfully.  Many other machines have not yet been updated.
>
> The following machines have had little to no effort since this email went out
> and do not even launch bitbake correctly anymore:
>
>     - centriq2400-rep
>     - dl360poc
>     - e3c246d4i
>     - ethanolx
>     - evb-zx3-pm3
>     - f0b
>     - fp5280g2
>     - g220a
>     - hr630
>     - hr855xg2
>     - kudo
>     - lanyang
>     - mtjade
>     - neptune
>     - nicole
>     - olympus
>     - olympus-nuvoton
>     - on6263m5
>     - quanta-q71l
>     - s2600wf
>     - stardragon4800-rep2
>     - thor
>     - x11spi
>
> Any machine not updated by October 15, 2021, I will assume is unused and
> unsupported and will create commits for removal.
>
> --
> Patrick Williams

g220a is updated now


-- 
BRs,
Lei YU

  reply	other threads:[~2021-08-13  3:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-06 14:19 Yocto override syntax change Patrick Williams
2021-08-08  1:02 ` Patrick Williams
2021-08-10 22:23   ` Patrick Williams
2021-08-12 12:41 ` Patrick Williams
2021-08-13  3:19   ` Lei Yu [this message]
2021-10-13  2:58   ` Patrick Williams

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=CAGm54UHNeYu9vEcL8R98UMn8qEsSQ6yNK3PUX_dzixzh2n_9gA@mail.gmail.com \
    --to=yulei.sh@bytedance.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=patrick@stwcx.xyz \
    /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;
as well as URLs for NNTP newsgroup(s).