Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Deepthi.Hemraj@eng.windriver.com
To: openembedded-core@lists.openembedded.org
Subject: Re: [mickledore][PATCH] glibc: Fix CVE-2023-5156
Date: Wed, 04 Oct 2023 02:37:21 -0700	[thread overview]
Message-ID: <20684.1696412241982587852@lists.openembedded.org> (raw)
In-Reply-To: <CAOSpxdZLgu7R0AEz4Cj2m_LcVzGE=P2p3G58WUjMYfuGxhnGyw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 399 bytes --]

There are 2 files in the patch sent and the first patch(0024-CVE-2023-5156-1.patch) is the duplicate of https://lists.openembedded.org/g/openembedded-core/message/188490 (CVE-2023-4806) ( https://lists.openembedded.org/g/openembedded-core/message/188490(CVE-2023-4806) ) which was sent to the mailing list.
Will I have to drop the (0024-CVE-2023-5156-1.patch) and send the second patch as a V2 ??

[-- Attachment #2: Type: text/html, Size: 1204 bytes --]

  reply	other threads:[~2023-10-04  9:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-03 11:29 [mickledore][PATCH] glibc: Fix CVE-2023-5156 Deepthi.Hemraj
2023-10-03 18:08 ` Steve Sakoman
2023-10-04  9:37   ` Deepthi.Hemraj [this message]
     [not found] ` <178AAB43CCCC6EBA.31348@lists.openembedded.org>
2023-10-04 14:27   ` [OE-core] " Steve Sakoman
2023-10-05 11:10     ` Shinde, Yash

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=20684.1696412241982587852@lists.openembedded.org \
    --to=deepthi.hemraj@eng.windriver.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