($INBOX_DIR/description missing)
 help / color / mirror / Atom feed
From: "Lee, Chee Yang" <chee.yang.lee@intel.com>
To: Michael Opdenacker <michael.opdenacker@bootlin.com>
Cc: "docs@lists.yoctoproject.org" <docs@lists.yoctoproject.org>
Subject: RE: [docs] [PATCH] migration-guides: add release notes for 4.3.1
Date: Wed, 29 Nov 2023 01:22:03 +0000	[thread overview]
Message-ID: <CH3PR11MB80938187B6CD704EE260C44FB983A@CH3PR11MB8093.namprd11.prod.outlook.com> (raw)
In-Reply-To: <62fb1e4d-2983-49f4-8135-3e8d5a98de1f@bootlin.com>



> -----Original Message-----
> From: Michael Opdenacker <michael.opdenacker@bootlin.com>
> Sent: Tuesday, November 28, 2023 7:02 PM
> 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.3.1
> 
> Hi Lee
> 
> Many thanks for the release notes!
> See my comments below...
> 
> On 28.11.23 at 07:50, 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.3.rst          |   1 +
> >   .../migration-guides/release-notes-4.3.1.rst  | 236 ++++++++++++++++++
> >   2 files changed, 237 insertions(+)
> >   create mode 100644
> > documentation/migration-guides/release-notes-4.3.1.rst
> >
> > diff --git a/documentation/migration-guides/release-4.3.rst
> > b/documentation/migration-guides/release-4.3.rst
> > index 92516ae8f..5b651a2ef 100644
> > --- a/documentation/migration-guides/release-4.3.rst
> > +++ b/documentation/migration-guides/release-4.3.rst
> > @@ -7,3 +7,4 @@ Release 4.3 (nanbield)
> >
> >      migration-4.3
> >      release-notes-4.3
> > +   release-notes-4.3.1
> > diff --git a/documentation/migration-guides/release-notes-4.3.1.rst
> > b/documentation/migration-guides/release-notes-4.3.1.rst
> > new file mode 100644
> > index 000000000..a9ebcee9d
> > --- /dev/null
> > +++ b/documentation/migration-guides/release-notes-4.3.1.rst
> > @@ -0,0 +1,236 @@
> > +.. SPDX-License-Identifier: CC-BY-SA-2.0-UK
> > +
> > +Release notes for Yocto-4.3.1 (Nanbield)
> > +----------------------------------------
> > +
> > +Security Fixes in Yocto-4.3.1
> > +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > +
> > +-  libsndfile1: Fix :cve:`2022-33065`
> > +-  libxml2: Ignore :cve:`2023-45322`
> > +-  linux-yocto: Ignore :cve:`2020-27418`, :cve:`2020-27418`,
> 
> 
> Oops, you mentioned 2020-27418 twice. Fixed, but if you meant another one
> instead, let me know.

Thanks for catching this.
I meant to mention by linux-yocto/6.1 and linux-yocto/6.5 but somehow mixed into single line. Will send a V2 to split them.
  






      reply	other threads:[~2023-11-29  1:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-28  6:50 [PATCH] migration-guides: add release notes for 4.3.1 chee.yang.lee
2023-11-28 11:01 ` [docs] " Michael Opdenacker
2023-11-29  1:22   ` Lee, Chee Yang [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=CH3PR11MB80938187B6CD704EE260C44FB983A@CH3PR11MB8093.namprd11.prod.outlook.com \
    --to=chee.yang.lee@intel.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=michael.opdenacker@bootlin.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).