Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Anuj Mittal <anuj.mittal@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [honister][PATCH 00/17] Pull request (cover letter only)
Date: Thu, 18 Nov 2021 14:48:54 +0800	[thread overview]
Message-ID: <cover.1637218024.git.anuj.mittal@intel.com> (raw)

Please merge these changes.

Thanks,

Anuj

The following changes since commit d2cba06c27c87c64423636153c0f186c5f45b147:

  glibc-version.inc: remove branch= from GLIBC_GIT_URI (2021-11-12 10:57:32 +0800)

are available in the Git repository at:

  git://push.openembedded.org/openembedded-core-contrib stable/honister-next

Bruce Ashfield (4):
  linux-yocto/5.14: update to v5.14.16
  linux-yocto/5.10: update to v5.10.77
  linux-yocto/5.14: update to v5.14.17
  linux-yocto/5.10: update to v5.10.78

Chen Qi (1):
  avahi: update CVE id fixed by local-ping.patch

Jon Mason (1):
  scripts/lib/wic/help.py: Update Fedora Kickstart URLs

Kai Kang (2):
  squashfs-tools: follow-up fix for CVE-2021-41072
  convert-srcuri.py: use regex to check space in SRC_URI

Peter Kjellerstedt (1):
  insane.bbclass: Add a check for directories that are expected to be
    empty

Richard Purdie (6):
  mirrors: Add uninative mirror on kernel.org
  scripts/oe-package-browser: Fix after overrides change
  scripts/oe-package-browser: Handle no packages being built
  wpa-supplicant: Match package override to PACKAGES for pkg_postinst
  uninative: Add version to uninative tarball name
  mirrors: Add kernel.org sources mirror for downloads.yoctoproject.org

Ross Burton (2):
  vim: fix CVE-2021-3796, CVE-2021-3872, and CVE-2021-3875
  vim: add patch number to CVE-2021-3778 patch

 meta/classes/insane.bbclass                   | 30 ++++++
 meta/classes/mirrors.bbclass                  |  2 +
 meta/classes/uninative.bbclass                |  2 +-
 meta/conf/distro/include/yocto-uninative.inc  |  3 +-
 meta/conf/documentation.conf                  |  2 +
 .../avahi/files/local-ping.patch              |  1 +
 .../wpa-supplicant/wpa-supplicant_2.9.bb      |  2 +-
 .../squashfs-tools/CVE-2021-41072.patch       |  6 +-
 .../linux/linux-yocto-rt_5.10.bb              |  6 +-
 .../linux/linux-yocto-rt_5.14.bb              |  6 +-
 .../linux/linux-yocto-tiny_5.10.bb            |  8 +-
 .../linux/linux-yocto-tiny_5.14.bb            |  8 +-
 meta/recipes-kernel/linux/linux-yocto_5.10.bb | 24 ++---
 meta/recipes-kernel/linux/linux-yocto_5.14.bb | 26 ++---
 ...28-using-freed-memory-when-replacing.patch | 83 ++++++++++++++++
 ...llegal-memory-access-if-buffer-name-.patch | 86 ++++++++++++++++
 ...ml_get-error-after-search-with-range.patch | 72 ++++++++++++++
 ...nvalid-memory-access-when-scrolling-.patch | 97 +++++++++++++++++++
 .../vim/files/CVE-2021-3778.patch             | 37 ++++---
 meta/recipes-support/vim/vim.inc              |  8 +-
 scripts/contrib/convert-srcuri.py             |  8 +-
 scripts/lib/wic/help.py                       |  4 +-
 scripts/oe-pkgdata-browser                    |  8 +-
 23 files changed, 464 insertions(+), 65 deletions(-)
 create mode 100644 meta/recipes-support/vim/files/0002-patch-8.2.3428-using-freed-memory-when-replacing.patch
 create mode 100644 meta/recipes-support/vim/files/0003-patch-8.2.3487-illegal-memory-access-if-buffer-name-.patch
 create mode 100644 meta/recipes-support/vim/files/0004-patch-8.2.3489-ml_get-error-after-search-with-range.patch
 create mode 100644 meta/recipes-support/vim/files/0005-patch-8.2.3564-invalid-memory-access-when-scrolling-.patch

-- 
2.33.1



             reply	other threads:[~2021-11-18  6:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-18  6:48 Anuj Mittal [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-02-08  1:28 [honister][PATCH 00/17] Pull request (cover letter only) Anuj Mittal

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.1637218024.git.anuj.mittal@intel.com \
    --to=anuj.mittal@intel.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