Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: "Armin Kuster" <akuster808@gmail.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [oe] [hardknott 0/6] Patch review April 24th
Date: Sun, 25 Apr 2021 15:34:36 -0700	[thread overview]
Message-ID: <d271c705-e4f1-7003-555e-217901b8c32e@gmail.com> (raw)
In-Reply-To: <CA+chaQdcK1_kimSqjafGH4b5Ek+gGE2P2fLrDYJ15dGmrNpqvA@mail.gmail.com>



On 4/25/21 2:41 PM, Martin Jansa wrote:
>
>
> On Sun, Apr 25, 2021 at 1:56 PM akuster808 <akuster808@gmail.com
> <mailto:akuster808@gmail.com>> wrote:
>
>
>
>     On 4/24/21 3:36 AM, Martin Jansa wrote:
>     > Please take
>     >
>     https://git.openembedded.org/meta-openembedded/commit/?id=b5ad9c011db2581cc84e5daa139acf73a0f6f5c0
>     > as well to fix
>     >
>     https://git.openembedded.org/meta-openembedded/commit/?h=hardknott&id=98a26903f770aa8698770817bdaf6175367917e1
>     > merged in previous PR.
>
>     Hardknott already has that commit. Was this meant for Gatesgarth?
>
>
> I don't see b5ad9c011db2581cc84e5daa139acf73a0f6f5c0 in hardknott nor
> in hardknott-next:
> https://git.openembedded.org/meta-openembedded/log/?h=hardknott-next&qt=grep&q=tbb
>
> And in master it's between the last 2 commits you did cherry-pick for
> hardknott in this round, so I don't understand why this one was skipped.
All will right itself soon. I think its a timing issue.
see stable/hardknott-nut.

-armin
>
> It's not needed in gatesgarth, because the tbb upgrade which dropped
> in PE wasn't merged to gatesgarth.


      reply	other threads:[~2021-04-25 22:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-24 10:11 [hardknott 0/6] Patch review April 24th Armin Kuster
2021-04-24 10:11 ` [hardknott 1/6] v4l-utils: fix reproducibility Armin Kuster
2021-04-24 10:11 ` [hardknott 2/6] python3-django: fix CVE-2021-28658 Armin Kuster
2021-04-24 10:11 ` [hardknott 3/6] tigervnc: upgrade to 1.11.0 Armin Kuster
2021-04-24 10:11 ` [hardknott 4/6] python3-django: upgrade to 2.2.20 Armin Kuster
2021-04-24 10:11 ` [hardknott 5/6] php: Upgrade to 7.4.16 Armin Kuster
2021-04-24 10:11 ` [hardknott 6/6] python3-cryptography: Upgrade to 3.3.2 Armin Kuster
2021-04-24 10:36 ` [oe] [hardknott 0/6] Patch review April 24th Martin Jansa
2021-04-25 20:56   ` Armin Kuster
2021-04-25 21:41     ` Martin Jansa
2021-04-25 22:34       ` Armin Kuster [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=d271c705-e4f1-7003-555e-217901b8c32e@gmail.com \
    --to=akuster808@gmail.com \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /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