From: Ross Burton <Ross.Burton@arm.com>
To: "Mali, Narpat" <Narpat.Mali@windriver.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>,
"Polampalli, Archana" <Archana.Polampalli@windriver.com>,
"G Pillai, Hari" <Hari.GPillai@windriver.com>
Subject: Re: [OE-core][PATCH 1/2] ffmpeg: fix for CVE-2022-3964
Date: Tue, 29 Nov 2022 13:42:40 +0000 [thread overview]
Message-ID: <A08B60F3-4D6A-47EC-9B50-C498375B1CBD@arm.com> (raw)
In-Reply-To: <DM4PR11MB5550E919066CC47698276611E4129@DM4PR11MB5550.namprd11.prod.outlook.com>
Yes, please.
> On 29 Nov 2022, at 07:49, Mali, Narpat <Narpat.Mali@windriver.com> wrote:
>
> Sure Ross, will make sure to add CVE tag in the patch header.
> Do I need to send again this patch with CVE tag ?
next prev parent reply other threads:[~2022-11-29 13:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 14:20 [OE-core][PATCH 1/2] ffmpeg: fix for CVE-2022-3964 Narpat Mali
2022-11-28 17:34 ` Ross Burton
2022-11-29 7:49 ` Mali, Narpat
2022-11-29 13:42 ` Ross Burton [this message]
2022-11-30 14:07 ` Mali, Narpat
-- strict thread matches above, loose matches on Subject: below --
2022-11-30 14:00 Narpat Mali
2022-11-30 14:58 ` Alexandre Belloni
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=A08B60F3-4D6A-47EC-9B50-C498375B1CBD@arm.com \
--to=ross.burton@arm.com \
--cc=Archana.Polampalli@windriver.com \
--cc=Hari.GPillai@windriver.com \
--cc=Narpat.Mali@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