public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: bruce.ashfield@gmail.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/6] kernel-yocto: consolidated pull request
Date: Wed, 09 Jul 2025 08:58:39 +0100	[thread overview]
Message-ID: <196cdceb3c5f14f1d3b0a58ef9c7020e3a39049b.camel@linuxfoundation.org> (raw)
In-Reply-To: <cover.1751985223.git.bruce.ashfield@gmail.com>

On Tue, 2025-07-08 at 10:36 -0400, bruce.ashfield@gmail.com wrote:
> I'm clearing the kernel queue now that I'm back at the office.
> 
> Following this will be libc-header updates and a bump to the new
> release/reference kernel version (v6.15 ... or possibly v6.16)
> depending
> on the timing of the upstream release.

Thanks, I tested these and things seem ok so they've merged.

You asked about updating the CVE list, we do need to do that. I looked
up the commands and those appear to be:

git clone https://github.com/CVEProject/cvelistV5
meta/recipes-kernel/linux/generate-cve-exclusions.py /my/checkout/cvelistV5/ 6.12.36 > meta/recipes-kernel/linux/cve-exclusion_6.12.inc

Cheers,

Richard


  parent reply	other threads:[~2025-07-09  7:58 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-08 14:36 [PATCH 0/6] kernel-yocto: consolidated pull request bruce.ashfield
2025-07-08 14:36 ` [PATCH 1/6] linux-yocto/6.12: update to v6.12.32 bruce.ashfield
2025-07-08 14:36 ` [PATCH 2/6] linux-yocto/6.12: yaffs2: silence warnings bruce.ashfield
2025-07-08 14:36 ` [PATCH 3/6] linux-yocto/6.12: update to v6.12.33 bruce.ashfield
2025-07-08 14:36 ` [PATCH 4/6] linux-yocto/6.12: riscv tune fragments bruce.ashfield
2025-07-08 14:36 ` [PATCH 5/6] linux-yocto/6.12: update to v6.12.34 bruce.ashfield
2025-07-08 14:36 ` [PATCH 6/6] linux-yocto/6.12: update to v6.12.36 bruce.ashfield
2025-07-09  7:58 ` Richard Purdie [this message]
2025-07-09 13:01   ` [PATCH 0/6] kernel-yocto: consolidated pull request Bruce Ashfield
  -- strict thread matches above, loose matches on Subject: below --
2025-05-06 16:32 bruce.ashfield
2024-12-10 21:06 bruce.ashfield
2024-11-21  4:13 bruce.ashfield
2024-11-21 16:50 ` Richard Purdie
2022-04-04 15:19 bruce.ashfield
2021-07-29  4:49 Bruce Ashfield
2021-06-16 20:48 Bruce Ashfield
2017-07-11 15:04 Bruce Ashfield
2017-06-08 19:21 Bruce Ashfield
2016-08-15 18:26 Bruce Ashfield
2016-08-16 16:00 ` Burton, Ross
2016-08-16 16:01   ` Bruce Ashfield
2016-08-16 16:10     ` Burton, Ross
2016-08-16 16:11       ` Bruce Ashfield
2016-08-16 16:15         ` Burton, Ross

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=196cdceb3c5f14f1d3b0a58ef9c7020e3a39049b.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bruce.ashfield@gmail.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