From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: Lee Chee Yang <chee.yang.lee@intel.com>
Cc: ypa.takayasu.ito@gmail.com, docs@lists.yoctoproject.org
Subject: Re: [docs] [PATCH] migration-guides: add release notes for 4.0.15
Date: Mon, 18 Dec 2023 10:54:07 +0100 [thread overview]
Message-ID: <4e2e29ee-1006-47cc-97c5-ec83550b2765@bootlin.com> (raw)
In-Reply-To: <20231218071724.2934824-1-chee.yang.lee@intel.com>
Hi Lee
Many thanks for the new release notes!
Just one comment below...
On 18.12.23 at 08:17, Lee Chee Yang wrote:
> From: Lee Chee Yang <chee.yang.lee@intel.com>
>
> Signed-off-by: Lee Chee Yang <chee.yang.lee@intel.com>
> ---
> .../migration-guides/release-4.0.rst | 1 +
> .../migration-guides/release-notes-4.0.15.rst | 189 ++++++++++++++++++
> 2 files changed, 190 insertions(+)
> create mode 100644 documentation/migration-guides/release-notes-4.0.15.rst
>
> diff --git a/documentation/migration-guides/release-4.0.rst b/documentation/migration-guides/release-4.0.rst
> index 748eab3bd..09fb8ca04 100644
> --- a/documentation/migration-guides/release-4.0.rst
> +++ b/documentation/migration-guides/release-4.0.rst
> @@ -21,3 +21,4 @@ Release 4.0 (kirkstone)
> release-notes-4.0.12
> release-notes-4.0.13
> release-notes-4.0.14
> + release-notes-4.0.15
> diff --git a/documentation/migration-guides/release-notes-4.0.15.rst b/documentation/migration-guides/release-notes-4.0.15.rst
> new file mode 100644
> index 000000000..301cc3f45
> --- /dev/null
> +++ b/documentation/migration-guides/release-notes-4.0.15.rst
> @@ -0,0 +1,189 @@
> +.. SPDX-License-Identifier: CC-BY-SA-2.0-UK
> +
> +Release notes for Yocto-4.0.15 (Kirkstone)
> +------------------------------------------
> +
> +Security Fixes in Yocto-4.0.15
> +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> +
> +- avahi: Fix :cve:`2023-1981`, :cve:`2023-38469`, :cve:`2023-38470`, :cve:`2023-38471`, :cve:`2023-38472` and :cve:`2023-38473`
> +- binutils: Fix :cve:`2022-47007`, :cve:`2022-47010` and :cve:`2022-48064`
> +- bluez5: Fix :cve:`2023-45866`
> +- ghostscript: Ignore GhostPCL :cve:`2023-38560`
> +- gnutls: Fix :cve:`2023-5981`
> +- go: Ignore :cve:`2023-45283` and :cve:`2023-45284`
> +- grub: Fix :cve:`2023-4692` and :cve:`2023-4693`
> +- gstreamer1.0-plugins-bad: Fix :cve_mitre:`2023-44429`
> +- libsndfile: Fix :cve:`2022-33065`
> +- libwebp: Fix :cve:`2023-4863`
> +- openssl: Fix :cve:`2023-5678`
> +- python3-cryptography: Fix :cve:`2023-49083`
> +- qemu: Fix :cve:`2023-1544`
> +- sudo: CVE-2023-42456 :cve_mitre:`2023-42465`
Oops, you forgot a ":cve:" macro here. Fixed.
Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Merged into "master-next".
Cheers
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2023-12-18 9:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 7:17 [PATCH] migration-guides: add release notes for 4.0.15 chee.yang.lee
2023-12-18 9:54 ` Michael Opdenacker [this message]
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=4e2e29ee-1006-47cc-97c5-ec83550b2765@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=chee.yang.lee@intel.com \
--cc=docs@lists.yoctoproject.org \
--cc=ypa.takayasu.ito@gmail.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).