From: Gyorgy Sarvari <skandigraun@gmail.com>
To: steve@sakoman.com, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core][scarthgap 03/16] binutils: Fix CVE-2025-7545
Date: Fri, 25 Jul 2025 07:10:51 +0200 [thread overview]
Message-ID: <cdf6356e-44b0-4151-aedc-5375355e164a@gmail.com> (raw)
In-Reply-To: <5c0c7058484fd8b1a82c2c810f7bccf016ea482b.1753392770.git.steve@sakoman.com>
On 7/24/25 23:35, Steve Sakoman via lists.openembedded.org wrote:
> --- a/meta/recipes-devtools/binutils/binutils-2.42.inc
> +++ b/meta/recipes-devtools/binutils/binutils-2.42.inc
> @@ -53,6 +53,10 @@ SRC_URI = "\
> file://CVE-2025-1179.patch \
> file://0022-CVE-2025-5245.patch \
> file://0022-CVE-2025-5244.patch \
> +<<<<<<< HEAD
> file://0023-CVE-2025-7546.patch \
> +=======
> + file://0023-CVE-2025-7545.patch \
> +>>>>>>> binutils: Fix CVE-2025-7545
> "
This looks like a merge conflict.
next prev parent reply other threads:[~2025-07-25 5:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 21:35 [OE-core][scarthgap 00/16] Patch review Steve Sakoman
2025-07-24 21:35 ` [OE-core][scarthgap 01/16] libxml2: fix CVE-2025-49795 Steve Sakoman
2025-07-24 21:35 ` [OE-core][scarthgap 02/16] binutils: Fix CVE-2025-7546 Steve Sakoman
2025-07-24 21:35 ` [OE-core][scarthgap 03/16] binutils: Fix CVE-2025-7545 Steve Sakoman
2025-07-25 5:10 ` Gyorgy Sarvari [this message]
2025-07-25 13:05 ` Steve Sakoman
2025-07-24 21:35 ` [OE-core][scarthgap 04/16] sqlite3: fix CVE-2025-6965 Steve Sakoman
2025-07-24 21:35 ` [OE-core][scarthgap 05/16] orc: set CVE_PRODUCT Steve Sakoman
2025-07-24 21:35 ` [OE-core][scarthgap 06/16] openssl: CVE-2024-41996 Steve Sakoman
2025-07-24 21:35 ` [OE-core][scarthgap 07/16] openssl: patch CVE-2025-27587 Steve Sakoman
2025-07-24 21:35 ` [OE-core][scarthgap 08/16] libpam: fix CVE-2025-6020 Steve Sakoman
2025-07-24 21:35 ` [OE-core][scarthgap 09/16] glibc: stable 2.39 branch updates Steve Sakoman
2025-07-24 21:35 ` [OE-core][scarthgap 10/16] xserver-xorg: upgrade 21.1.6 -> 21.1.18 Steve Sakoman
2025-07-24 21:35 ` [OE-core][scarthgap 11/16] mtools: upgrade 4.0.43 -> 4.0.44 Steve Sakoman
2025-07-24 21:35 ` [OE-core][scarthgap 12/16] mtools: upgrade 4.0.44 -> 4.0.45 Steve Sakoman
2025-07-24 21:35 ` [OE-core][scarthgap 13/16] mtools: upgrade 4.0.45 -> 4.0.46 Steve Sakoman
2025-07-24 21:35 ` [OE-core][scarthgap 14/16] mtools: upgrade 4.0.46 -> 4.0.47 Steve Sakoman
2025-07-24 21:35 ` [OE-core][scarthgap 15/16] mtools: upgrade 4.0.47 -> 4.0.48 Steve Sakoman
2025-07-24 21:35 ` [OE-core][scarthgap 16/16] mtools: upgrade 4.0.48 -> 4.0.49 Steve Sakoman
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=cdf6356e-44b0-4151-aedc-5375355e164a@gmail.com \
--to=skandigraun@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=steve@sakoman.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