From: Yash Shinde <yashinde145@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: rwmacleod@gmail.com, umesh.kalappa0@gmail.com,
pgowda.cve@gmail.com, shivams@gmail.com,
sundeep.kokkonda@gmail.com, Yash Shinde <yashinde145@gmail.com>
Subject: [kirkstone] binutils: stable 2.38 branch updates
Date: Mon, 24 Oct 2022 12:47:47 +0530 [thread overview]
Message-ID: <20221024071747.1998470-1-yashinde145@gmail.com> (raw)
Below commits on binutils-2.38 stable branch are updated.
dc2474e7d20 (HEAD -> binutils-2_38-branch, origin/binutils-2_38-branch) elf: Reset alignment for each PT_LOAD segment
f184ba116ed Re: PowerPC64 pcrel got relocs against local symbols
737e29d05eb PowerPC64 pcrel got relocs against local symbols
Signed-off-by: Yash Shinde <yashinde145@gmail.com>
---
meta/recipes-devtools/binutils/binutils-2.38.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-devtools/binutils/binutils-2.38.inc b/meta/recipes-devtools/binutils/binutils-2.38.inc
index fc88d4a79e..acb2de04f9 100644
--- a/meta/recipes-devtools/binutils/binutils-2.38.inc
+++ b/meta/recipes-devtools/binutils/binutils-2.38.inc
@@ -18,7 +18,7 @@ SRCBRANCH ?= "binutils-2_38-branch"
UPSTREAM_CHECK_GITTAGREGEX = "binutils-(?P<pver>\d+_(\d_?)*)"
-SRCREV ?= "5c0b4ee406035917d0e50aa138194fab57ae6bf8"
+SRCREV ?= "dc2474e7d204c124ab5a21b4490aa46eb7e1d4c3"
BINUTILS_GIT_URI ?= "git://sourceware.org/git/binutils-gdb.git;branch=${SRCBRANCH};protocol=git"
SRC_URI = "\
${BINUTILS_GIT_URI} \
--
2.25.1
next reply other threads:[~2022-10-24 7:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 7:17 Yash Shinde [this message]
2022-10-24 7:20 ` [kirkstone] binutils: stable 2.38 branch updates Yash Shinde
-- strict thread matches above, loose matches on Subject: below --
2022-08-01 10:11 [OE-core] " Khem Raj
2022-09-13 9:43 ` Sundeep KOKKONDA
2022-08-01 2:24 Sundeep KOKKONDA
2022-08-01 2:34 ` Sundeep KOKKONDA
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=20221024071747.1998470-1-yashinde145@gmail.com \
--to=yashinde145@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=pgowda.cve@gmail.com \
--cc=rwmacleod@gmail.com \
--cc=shivams@gmail.com \
--cc=sundeep.kokkonda@gmail.com \
--cc=umesh.kalappa0@gmail.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