public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: bruce.ashfield@gmail.com
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/5] linux-yocto: consolidated pull request
Date: Sun, 11 Aug 2024 14:04:18 -0400	[thread overview]
Message-ID: <cover.1723399246.git.bruce.ashfield@gmail.com> (raw)

From: Bruce Ashfield <bruce.ashfield@gmail.com>

Richard,

This is mainly a v3 of the 6.10 introduction series, but I've
also included a 6.6 version bump and 6.11 for -dev.

This should fix the:

  - trap seen on multiple machines with 6.10.3, I've disabled a
    NFS option that was introduced in .3 (and shoulldn't have
    been)
  - I've updated -rt to fix the build issue

As I mentioned in another reply, the config warning that showed
up on meta-virt shouldn't have happened, since the Kconfig option
in question was removed from the kernel-cache about three weeks
ago. If that warning comes back, I'll want to have a look at the
SRCREVs being built to see what is going on!

Bruce

The following changes since commit b997e4dc9cce85afeddf5c53b094e00379f7caae:

  ffmpeg: fix build with binutils 2.43 on arm with commerical codecs (2024-08-09 22:33:38 +0100)

are available in the Git repository at:

  https://git.yoctoproject.org/poky-contrib zedd/kernel
  https://git.yoctoproject.org/poky-contrib/log/?h=zedd/kernel

Bruce Ashfield (5):
  linux-yocto-dev: bump to v6.11
  linux-yocto-rt/6.10: update to -rt14
  linux-yocto/6.10: cfg: disable nfsd legacy client tracking
  linux-yocto/6.6: update to v6.6.44
  poky/poky-tiny: bump preferred version to 6.10

 meta-poky/conf/distro/poky-tiny.conf          |  2 +-
 meta-poky/conf/distro/poky.conf               |  4 +--
 meta/recipes-kernel/linux/linux-yocto-dev.bb  |  4 +--
 .../linux/linux-yocto-rt_6.10.bb              |  4 +--
 .../linux/linux-yocto-rt_6.6.bb               |  6 ++--
 .../linux/linux-yocto-tiny_6.10.bb            |  2 +-
 .../linux/linux-yocto-tiny_6.6.bb             |  6 ++--
 meta/recipes-kernel/linux/linux-yocto_6.10.bb |  2 +-
 meta/recipes-kernel/linux/linux-yocto_6.6.bb  | 28 +++++++++----------
 9 files changed, 29 insertions(+), 29 deletions(-)

-- 
2.39.2



             reply	other threads:[~2024-08-11 18:04 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-11 18:04 bruce.ashfield [this message]
2024-08-11 18:04 ` [PATCH 1/5] linux-yocto-dev: bump to v6.11 bruce.ashfield
2024-09-24 13:01   ` [OE-core] " Quentin Schulz
2024-09-24 14:11     ` Bruce Ashfield
2024-09-25 13:37       ` Quentin Schulz
2024-09-25 13:57         ` Bruce Ashfield
2024-09-25 14:06           ` Quentin Schulz
2024-09-25 14:23             ` Bruce Ashfield
2024-09-30 10:09               ` Quentin Schulz
2024-10-01 14:08                 ` Bruce Ashfield
2024-09-25 16:10         ` Ross Burton
2024-08-11 18:04 ` [PATCH 2/5] linux-yocto-rt/6.10: update to -rt14 bruce.ashfield
2024-08-11 18:04 ` [PATCH 3/5] linux-yocto/6.10: cfg: disable nfsd legacy client tracking bruce.ashfield
2024-08-11 18:04 ` [PATCH 4/5] linux-yocto/6.6: update to v6.6.44 bruce.ashfield
2024-08-11 18:04 ` [PATCH 5/5] poky/poky-tiny: bump preferred version to 6.10 bruce.ashfield
2024-08-12  9:47 ` [PATCH 0/5] linux-yocto: consolidated pull request Richard Purdie
2024-08-12 12:47   ` Bruce Ashfield
  -- strict thread matches above, loose matches on Subject: below --
2023-02-01 16:28 bruce.ashfield
2020-11-19 19:17 Bruce Ashfield
2020-05-29  1:29 Bruce Ashfield
2020-05-03 15:44 Bruce Ashfield
2020-05-04  8:30 ` Richard Purdie
2020-05-04 12:56   ` Bruce Ashfield
2020-03-24 23:04 Bruce Ashfield
2016-07-27 16:57 Bruce Ashfield
2016-06-21 15:20 Bruce Ashfield
2016-04-13 16:12 Bruce Ashfield
2015-05-01  1:34 Bruce Ashfield
2015-05-01 22:59 ` Richard Purdie
2015-05-01 23:30   ` Bruce Ashfield
2015-05-02  8:13     ` Martin Jansa
2015-05-03  2:50       ` Bruce Ashfield
2015-05-06 14:42         ` Martin Jansa
2015-05-06 14:58           ` Bruce Ashfield
2015-05-06 15:33             ` Martin Jansa
2015-05-06 15:44               ` Richard Purdie
2015-05-06 16:07                 ` Martin Jansa
2015-05-06 17:46                   ` Bruce Ashfield
2015-05-06 21:32                     ` Richard Purdie
2015-05-06 22:49                       ` Martin Jansa
2015-05-07 15:33                         ` Bruce Ashfield
2015-05-07  6:33               ` Khem Raj
2015-05-02  9:00     ` Richard Purdie
2015-05-03  2:53       ` Bruce Ashfield
2015-05-03  3:52       ` Bruce Ashfield
2015-05-03 10:48         ` Richard Purdie
2015-05-03 21:30 ` Richard Purdie
2015-05-04  4:36   ` Bruce Ashfield
2015-05-04 15:01   ` Bruce Ashfield
2015-03-24 18:57 Bruce Ashfield
2015-03-25  9:26 ` Richard Purdie
2015-03-25 12:13   ` Bruce Ashfield
2015-03-25 13:26     ` Bruce Ashfield
2015-03-25 13:52       ` Richard Purdie
2013-08-23 18:08 Bruce Ashfield
2013-08-23 21:30 ` Bruce Ashfield
2013-08-24  6:33 ` Saul Wold
2013-08-24 13:34   ` Bruce Ashfield
2013-08-24 13:45     ` Bruce Ashfield
2013-08-24 13:50       ` Saul Wold
2013-08-24 13:53         ` Bruce Ashfield
2013-08-24 14:47         ` Bruce Ashfield
2013-08-24 14:59         ` Bruce Ashfield
2013-08-24 16:05         ` Bruce Ashfield
2012-02-05  6:31 Bruce Ashfield
2012-02-08  4:09 ` Saul Wold
2012-01-11 18:52 Bruce Ashfield
2012-01-17 19:28 ` Saul Wold

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.1723399246.git.bruce.ashfield@gmail.com \
    --to=bruce.ashfield@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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