From: "Deepak Rathore" <deeratho@cisco.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [whinlatter][PATCH 1/4] binutils: Fix CVE-2025-69648
Date: Wed, 01 Apr 2026 03:05:34 -0700 [thread overview]
Message-ID: <787045.1775037934082826911@lists.openembedded.org> (raw)
In-Reply-To: <DH75Z2970Q68.2IIP1XOVZ2EPX@smile.fr>
[-- Attachment #1: Type: text/plain, Size: 122 bytes --]
Thanks, Yoann, for your review.
I have corrected all the patches and sent to you for your review.
Regards,
Deepak
[-- Attachment #2: Type: text/html, Size: 200 bytes --]
next prev parent reply other threads:[~2026-04-01 10:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 4:12 [OE-core][whinlatter][PATCH 1/4] binutils: Fix CVE-2025-69648 Deepak Rathore -X (deeratho - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-03-17 4:12 ` [OE-core][whinlatter][PATCH v2 2/4] binutils: Fix CVE-2025-69644 CVE-2025-69647 Deepak Rathore -X (deeratho - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-03-19 23:56 ` [OE-core][whinlatter][PATCH 1/4] binutils: Fix CVE-2025-69648 Yoann Congal
2026-04-01 10:05 ` Deepak Rathore [this message]
2026-04-01 10:17 ` [OE-core] [whinlatter][PATCH " Yoann Congal
2026-04-02 7:14 ` Deepak Rathore
2026-04-01 10:00 ` [OE-core][whinlatter][PATCH v2 " Deepak Rathore -X (deeratho - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-04-01 10:15 ` Patchtest results for " patchtest
2026-04-01 10:19 ` Yoann Congal
2026-04-02 6:54 ` [OE-core][whinlatter][PATCH v3 " Deepak Rathore -X (deeratho - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-04-01 10:04 ` [OE-core][whinlatter][PATCH v3 4/4] binutils: Fix CVE-2025-69652 Deepak Rathore -X (deeratho - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-04-02 6:57 ` [OE-core][whinlatter][PATCH v4 3/4] binutils: Fix CVE-2025-69649 Deepak Rathore -X (deeratho - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-04-02 6:58 ` [OE-core][whinlatter][PATCH v4 4/4] binutils: Fix CVE-2025-69652 Deepak Rathore -X (deeratho - E INFOCHIPS PRIVATE LIMITED at Cisco)
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=787045.1775037934082826911@lists.openembedded.org \
--to=deeratho@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