public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Anil Dongare -X (adongare - E INFOCHIPS PRIVATE LIMITED at Cisco)" <adongare@cisco.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [scarthgap][PATCH 3/3] vim: ignore CVE-2025-66476
Date: Mon, 16 Feb 2026 02:10:47 -0800	[thread overview]
Message-ID: <920657.1771236647380325202@lists.openembedded.org> (raw)
In-Reply-To: <CAMSfU+6Bmh+wDLNK-tbJo1OdY2faqh4o+x4pEdAY7yQ0H7K9jg@mail.gmail.com>

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

Hello,
I hope this message finds you well. I am reaching out to follow up on the patch that was submitted by Ankur concerning the update for ***CVE-2025-66476*** in the *_scarthgap_* branch.
Could you please provide us with any updates regarding when this patch is anticipated to be merged?

Thank you very much in advance for your assistance.

Best regards,
Anil Dongare

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

  reply	other threads:[~2026-02-16 10:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-02  4:08 [OE-core][scarthgap][PATCH 1/3] ffmpeg: upgrade 6.1.3 -> 6.1.4 ankur.tyagi85
2026-02-02  4:08 ` [OE-core][scarthgap][PATCH 2/3] ffmpeg: ignore CVE-2025-25469 ankur.tyagi85
2026-02-05 15:10   ` Yoann Congal
2026-02-05 15:17     ` Yoann Congal
2026-02-05 22:16       ` Ankur Tyagi
2026-02-02  4:08 ` [OE-core][scarthgap][PATCH 3/3] vim: ignore CVE-2025-66476 ankur.tyagi85
2026-02-05  9:59   ` Yoann Congal
2026-02-16 10:10     ` Anil Dongare -X (adongare - E INFOCHIPS PRIVATE LIMITED at Cisco) [this message]
2026-02-16 10:46       ` [OE-core] [scarthgap][PATCH " Yoann Congal

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=920657.1771236647380325202@lists.openembedded.org \
    --to=adongare@cisco.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