public inbox for docs@lists.yoctoproject.org
 help / color / mirror / Atom feed
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: Lee Chee Yang <chee.yang.lee@intel.com>
Cc: docs@lists.yoctoproject.org
Subject: Re: [docs] [PATCH] migration-guides: add release notes for 4.0.12
Date: Tue, 5 Sep 2023 07:28:55 +0200	[thread overview]
Message-ID: <bdd026a8-39b5-4f9a-b50d-7f06bef1d466@bootlin.com> (raw)
In-Reply-To: <20230824144847.850298-1-chee.yang.lee@intel.com>

Hi Lee

Many thanks for the release notes!

On 24.08.23 at 16:48, 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.12.rst | 277 ++++++++++++++++++
>   2 files changed, 278 insertions(+)
>   create mode 100644 documentation/migration-guides/release-notes-4.0.12.rst
>
> diff --git a/documentation/migration-guides/release-4.0.rst b/documentation/migration-guides/release-4.0.rst
> index 1f08c8844..688ea7ae0 100644
> --- a/documentation/migration-guides/release-4.0.rst
> +++ b/documentation/migration-guides/release-4.0.rst
> @@ -18,3 +18,4 @@ Release 4.0 (kirkstone)
>      release-notes-4.0.9
>      release-notes-4.0.10
>      release-notes-4.0.11
> +   release-notes-4.0.12
> diff --git a/documentation/migration-guides/release-notes-4.0.12.rst b/documentation/migration-guides/release-notes-4.0.12.rst
> new file mode 100644
> index 000000000..3dbbfcbed
> --- /dev/null
> +++ b/documentation/migration-guides/release-notes-4.0.12.rst
> @@ -0,0 +1,277 @@
> +.. SPDX-License-Identifier: CC-BY-SA-2.0-UK
> +
> +Release notes for Yocto-4.0.12 (Kirkstone)
> +------------------------------------------
> +
> +Security Fixes in Yocto-4.0.12
> +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> +
> +-  bind: Fix :cve:`2023-2828` and :cve:`2023-2911`
> +-  cups: Fix :cve:`2023-34241`
> +-  curl: Added :cve:`2023-28320` Follow-up patch
> +-  dbus: Fix :cve:`2023-34969`
> +-  dmidecode: fix :cve:`2023-30630`
> +-  ghostscript: fix :cve:`2023-36664`
> +-  go: fix :cve_mitre:`2023-24531`, :cve:`2023-24536`, :cve:`2023-29400`, :cve:`2023-29402`, :cve:`2023-29404`, :cve:`2023-29405` and :cve:`2023-29406`
> +-  libarchive: Ignore :cve:`2023-30571`
> +-  libcap: Fix :cve:`2023-2602` and :cve:`2023-2603`
> +-  libjpeg-turbo: Fix :cve:`2023-2804`
> +-  libpcre2: Fix :cve:`2022-41409`
> +-  libtiff: fix :cve:`2023-26965`
> +-  libwebp: Fix :cve:`2023-1999`
> +-  libx11: Fix :cve:`2023-3138`
> +-  libxpm: Fix :cve:`2022-44617`
> +-  ninja: Ignore :cve:`2021-4336`
> +-  openssh: Fix :cve:`2023-38408`
> +-  openssl: Fix :cve:`2023-2975`, :cve:`2023-3446` and :cve:`2023-3817`
> +-  perl: Fix :cve:`2023-31486`
> +-  python3: Ignore :cve:`2023-36632`
> +-  qemu: Fix :cve:`2023-0330`, :cve_mitre:`2023-2861`, :cve_mitre:`2023-3255` and :cve_mitre:`2023-3301`
> +-  sqlite3: Fix :cve:`2023-36191`
> +-  tiff: Fix :cve:`2023-0795`, :cve:`2023-0796`, :cve:`2023-0797`, :cve:`2023-0798`, :cve:`2023-0799`, :cve:`2023-25433`, :cve:`2023-25434` and :cve:`2023-25435`
> +-  vim: CVE-2023-2609 :cve:`2023-2610`


You forgot one ":cve:" macro in the last line, but I fixed it.
Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
and merged into "master-next".

Thanks again
Michael.

-- 
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



      reply	other threads:[~2023-09-05  5:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-24 14:48 [PATCH] migration-guides: add release notes for 4.0.12 chee.yang.lee
2023-09-05  5:28 ` 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=bdd026a8-39b5-4f9a-b50d-7f06bef1d466@bootlin.com \
    --to=michael.opdenacker@bootlin.com \
    --cc=chee.yang.lee@intel.com \
    --cc=docs@lists.yoctoproject.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