public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Steve Sakoman <steve@sakoman.com>
To: openembedded-core@lists.openembedded.org
Subject: [OE-core][dunfell 0/9] Patch review
Date: Thu, 22 Feb 2024 04:30:31 -1000	[thread overview]
Message-ID: <cover.1708612053.git.steve@sakoman.com> (raw)

Please review this set of changes for dunfell and have comments back by
end of day Monday, February 26

Passed a-full on autobuilder:

https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/6590

The following changes since commit 7ab6087536bc67c63094f08f863dcd3d5e35b8e7:

  cmake: Unset CMAKE_CXX_IMPLICIT_INCLUDE_DIRECTORIES (2024-02-12 17:13:14 -1000)

are available in the Git repository at:

  https://git.openembedded.org/openembedded-core-contrib stable/dunfell-nut
  http://cgit.openembedded.org/openembedded-core-contrib/log/?h=stable/dunfell-nut

Bruce Ashfield (5):
  linux-yocto/5.4: update to v5.4.264
  linux-yocto/5.4: update to v5.4.265
  linux-yocto/5.4: update to v5.4.266
  linux-yocto/5.4: update to v5.4.267
  linux-yocto/5.4: update to v5.4.268

Peter Marko (1):
  gcc-shared-source: whitelist CVE-2023-4039

Richard Purdie (1):
  sstatesig: Allow exclusion of the root directory for do_package

Steve Sakoman (1):
  cve-exclusion_5.4.inc: update for 5.4.268

Tim Orling (1):
  vim: upgrade v9.0.2130 -> v9.0.2190

 meta/lib/oe/sstatesig.py                      |   5 +-
 .../gcc/gcc-shared-source.inc                 |   3 +
 .../linux/cve-exclusion_5.4.inc               | 199 +++++++++++++++++-
 .../linux/linux-yocto-rt_5.4.bb               |   6 +-
 .../linux/linux-yocto-tiny_5.4.bb             |   8 +-
 meta/recipes-kernel/linux/linux-yocto_5.4.bb  |  22 +-
 meta/recipes-support/vim/vim.inc              |   4 +-
 7 files changed, 215 insertions(+), 32 deletions(-)

-- 
2.34.1



             reply	other threads:[~2024-02-22 14:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-22 14:30 Steve Sakoman [this message]
2024-02-22 14:30 ` [OE-core][dunfell 1/9] gcc-shared-source: whitelist CVE-2023-4039 Steve Sakoman
2024-02-22 14:30 ` [OE-core][dunfell 2/9] vim: upgrade v9.0.2130 -> v9.0.2190 Steve Sakoman
2024-02-22 14:30 ` [OE-core][dunfell 3/9] linux-yocto/5.4: update to v5.4.264 Steve Sakoman
2024-02-22 14:30 ` [OE-core][dunfell 4/9] linux-yocto/5.4: update to v5.4.265 Steve Sakoman
2024-02-22 14:30 ` [OE-core][dunfell 5/9] linux-yocto/5.4: update to v5.4.266 Steve Sakoman
2024-02-22 14:30 ` [OE-core][dunfell 6/9] linux-yocto/5.4: update to v5.4.267 Steve Sakoman
2024-02-22 14:30 ` [OE-core][dunfell 7/9] linux-yocto/5.4: update to v5.4.268 Steve Sakoman
2024-02-22 14:30 ` [OE-core][dunfell 8/9] cve-exclusion_5.4.inc: update for 5.4.268 Steve Sakoman
2024-02-22 14:47   ` Patchtest results for " patchtest
2024-02-22 14:30 ` [OE-core][dunfell 9/9] sstatesig: Allow exclusion of the root directory for do_package Steve Sakoman
  -- strict thread matches above, loose matches on Subject: below --
2023-04-30 16:25 [OE-core][dunfell 0/9] Patch review Steve Sakoman
2022-10-13 16:36 Steve Sakoman
2022-09-14  2:25 Steve Sakoman
2022-05-18  2:30 Steve Sakoman
2022-05-02 23:02 Steve Sakoman
2022-04-20 21:51 Steve Sakoman
2021-09-10 14:07 Steve Sakoman
2020-12-07 14:12 Steve Sakoman
2020-11-17 23:47 Steve Sakoman

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=cover.1708612053.git.steve@sakoman.com \
    --to=steve@sakoman.com \
    --cc=openembedded-core@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