Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Anuj Mittal" <anuj.mittal@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [hardknott][PATCH 00/15] pull request (cover letter only)
Date: Sat, 15 May 2021 22:31:15 +0800	[thread overview]
Message-ID: <cover.1621088943.git.anuj.mittal@intel.com> (raw)

Please merge these changes in hardknott.

Thanks,

Anuj

The following changes since commit d5d88c2293e8ebc958d1bce9af8f796024443be9:

  libevent: Increase ptest timing tolerance 50 ms -> 100 ms (2021-05-07 08:51:54 +0800)

are available in the Git repository at:

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

Alexander Kanavin (1):
  linux-firmware: upgrade 20210208 -> 20210315

Anuj Mittal (1):
  lsb-release: fix reproducibility failure

Bruce Ashfield (1):
  linux-yocto/5.4: qemuppc32: reduce serial shutdown issues

Chen Qi (1):
  db: update CVE_PRODUCT

Kai Kang (1):
  grub2.inc: remove '-O2' from CFLAGS

Michael Opdenacker (1):
  sanity.bbclass: mention CONNECTIVITY_CHECK_URIS in network failure
    message

Peter Kjellerstedt (1):
  libcap: Configure Make variables correctly without a horrible hack

Richard Purdie (4):
  oeqa/qemurunner: Improve logging thread exit handling for qemu
    shutdown test
  oeqa/qemurunner: Fix binary vs str issue
  oeqa/qemurunner: Improve handling of run_serial for shutdown commands
  puzzles: Upstream changed to main branch for development

Romain Naour (1):
  dejagnu: needs expect at runtime

Vinícius Ossanes Aquino (1):
  lttng-modules: backport patches to fix build against 5.12+ kernel

Yann Dirson (1):
  linux-firmware: include all relevant files in -bcm4356

zhengruoqin (1):
  ruby: upgrade 3.0.0 -> 3.0.1

 meta/classes/sanity.bbclass                   |   9 +-
 meta/lib/oeqa/selftest/cases/runqemu.py       |   9 +-
 meta/lib/oeqa/utils/qemurunner.py             |  21 +-
 meta/recipes-bsp/grub/grub2.inc               |   2 +
 .../recipes-devtools/dejagnu/dejagnu_1.6.2.bb |   1 +
 .../ruby/{ruby_3.0.0.bb => ruby_3.0.1.bb}     |   2 +-
 .../help2man-reproducibility.patch            |  27 ++
 meta/recipes-extended/lsb/lsb-release_1.4.bb  |   1 +
 ...20210208.bb => linux-firmware_20210315.bb} |   8 +-
 .../linux/linux-yocto-rt_5.4.bb               |   2 +-
 .../linux/linux-yocto-tiny_5.4.bb             |   2 +-
 meta/recipes-kernel/linux/linux-yocto_5.4.bb  |   2 +-
 ...block-add-a-disk_uevent-helper-v5.12.patch | 305 ++++++++++++++++++
 ...block-add-a-disk_uevent-helper-v5.12.patch |  48 +++
 ...free-event-name-mismatching-with-pro.patch |  71 ++++
 .../lttng/lttng-modules_2.12.5.bb             |   3 +
 meta/recipes-sato/puzzles/puzzles_git.bb      |   2 +-
 meta/recipes-support/db/db_5.3.28.bb          |   2 +-
 meta/recipes-support/libcap/libcap_2.48.bb    |  21 +-
 19 files changed, 504 insertions(+), 34 deletions(-)
 rename meta/recipes-devtools/ruby/{ruby_3.0.0.bb => ruby_3.0.1.bb} (97%)
 create mode 100644 meta/recipes-extended/lsb/lsb-release/help2man-reproducibility.patch
 rename meta/recipes-kernel/linux-firmware/{linux-firmware_20210208.bb => linux-firmware_20210315.bb} (99%)
 create mode 100644 meta/recipes-kernel/lttng/lttng-modules/0005-fix-block-add-a-disk_uevent-helper-v5.12.patch
 create mode 100644 meta/recipes-kernel/lttng/lttng-modules/0006-fix-backport-block-add-a-disk_uevent-helper-v5.12.patch
 create mode 100644 meta/recipes-kernel/lttng/lttng-modules/0007-fix-mm-tracing-kfree-event-name-mismatching-with-pro.patch

-- 
2.31.1


             reply	other threads:[~2021-05-15 14:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-15 14:31 Anuj Mittal [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-01-25  2:38 [hardknott][PATCH 00/15] Pull request (cover letter only) Anuj Mittal
2022-03-10  1:42 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.1621088943.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