From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Steve Sakoman <steve@sakoman.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core][kirkstone 01/27] ruby: add PACKAGECONFIG for capstone
Date: Thu, 14 Jul 2022 10:40:11 +0100 [thread overview]
Message-ID: <9af42266ee228614914afa3f1cf7ac1f43b550be.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAOSpxdad4+XpE-kWSbuWYu8YptOx-nDFthiuEPUcyBrx+dMpkw@mail.gmail.com>
On Wed, 2022-07-13 at 18:42 -1000, Steve Sakoman wrote:
> At this point I've only seen this on kirkstone, but I suspect it is
> only a matter of time before we see it on master too. So we should
> probably consider this for master too.
No probably about it, I've queued for testing!
Cheers,
Richard
prev parent reply other threads:[~2022-07-14 9:40 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 4:35 [OE-core][kirkstone 00/27] Patch review Steve Sakoman
2022-07-14 4:35 ` [OE-core][kirkstone 01/27] ruby: add PACKAGECONFIG for capstone Steve Sakoman
2022-07-14 4:35 ` [OE-core][kirkstone 02/27] qemu: " Steve Sakoman
2022-07-14 4:35 ` [OE-core][kirkstone 03/27] qemu: Avoid accidental librdmacm linkage Steve Sakoman
2022-07-14 4:35 ` [OE-core][kirkstone 04/27] qemu: Avoid accidental libvdeplug linkage Steve Sakoman
2022-07-14 4:35 ` [OE-core][kirkstone 05/27] harfbuzz: fix CVE-2022-33068 Steve Sakoman
2022-07-17 19:32 ` Pavel Zhukov
2022-07-14 4:35 ` [OE-core][kirkstone 06/27] tiff: backport the fix for CVE-2022-2056, CVE-2022-2057, and CVE-2022-2058 Steve Sakoman
2022-07-14 4:35 ` [OE-core][kirkstone 07/27] u-boot: fix CVE-2022-34835 Steve Sakoman
2022-07-14 4:35 ` [OE-core][kirkstone 08/27] vim: upgrade to 9.0.0021 Steve Sakoman
2022-07-14 4:35 ` [OE-core][kirkstone 09/27] openssl: update 3.0.4 -> 3.0.5 Steve Sakoman
2022-07-14 4:35 ` [OE-core][kirkstone 10/27] glibc: stable 2.35 branch updates Steve Sakoman
2022-07-24 17:54 ` Martin Jansa
2022-07-25 10:17 ` pgowda cve
2022-07-25 10:33 ` Martin Jansa
2022-07-25 10:51 ` pgowda cve
2022-07-14 4:35 ` [OE-core][kirkstone 11/27] glibc-tests: Avoid reproducibility issues Steve Sakoman
2022-07-14 4:35 ` [OE-core][kirkstone 12/27] binutils : stable 2.38 branch updates Steve Sakoman
2022-07-14 4:35 ` [OE-core][kirkstone 13/27] gstreamer1.0: upgrade 1.20.2 -> 1.20.3 Steve Sakoman
2022-07-14 4:35 ` [OE-core][kirkstone 14/27] gst-devtools: " Steve Sakoman
2022-07-14 4:35 ` [OE-core][kirkstone 15/27] gstreamer1.0-libav: " Steve Sakoman
2022-07-14 4:35 ` [OE-core][kirkstone 16/27] gstreamer1.0-omx: " Steve Sakoman
2022-07-14 4:35 ` [OE-core][kirkstone 17/27] gstreamer1.0-plugins-bad: " Steve Sakoman
2022-07-14 4:35 ` [OE-core][kirkstone 18/27] gstreamer1.0-plugins-base: " Steve Sakoman
2022-07-14 4:35 ` [OE-core][kirkstone 19/27] gstreamer1.0-plugins-good: " Steve Sakoman
2022-07-14 4:35 ` [OE-core][kirkstone 20/27] gstreamer1.0-plugins-ugly: " Steve Sakoman
2022-07-14 4:35 ` [OE-core][kirkstone 21/27] gstreamer1.0-python: " Steve Sakoman
2022-07-14 4:35 ` [OE-core][kirkstone 22/27] gstreamer1.0-rtsp-server: " Steve Sakoman
2022-07-14 4:35 ` [OE-core][kirkstone 23/27] gstreamer1.0-vaapi: " Steve Sakoman
2022-07-14 4:35 ` [OE-core][kirkstone 24/27] weston: update 10.0.0 -> 10.0.1 Steve Sakoman
2022-07-14 4:35 ` [OE-core][kirkstone 25/27] glib-2.0: upgrade 2.72.2 -> 2.72.3 Steve Sakoman
2022-07-14 4:35 ` [OE-core][kirkstone 26/27] glib-networking: upgrade 2.72.0 -> 2.72.1 Steve Sakoman
2022-07-14 4:35 ` [OE-core][kirkstone 27/27] libsoup: upgrade 3.0.6 -> 3.0.7 Steve Sakoman
[not found] ` <17019818268B4DB5.31059@lists.openembedded.org>
2022-07-14 4:42 ` [OE-core][kirkstone 01/27] ruby: add PACKAGECONFIG for capstone Steve Sakoman
2022-07-14 9:40 ` Richard Purdie [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=9af42266ee228614914afa3f1cf7ac1f43b550be.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=steve@sakoman.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox