public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Deepthi Hemraj <deepadeepthi98@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
Subject: [kirkstone][PATCH] glibc: stable 2.35 branch updates.
Date: Fri, 28 Apr 2023 13:59:47 +0530	[thread overview]
Message-ID: <20230428082947.4091975-1-deepadeepthi98@gmail.com> (raw)

Below commits on glibc-2.35 stable branch are updated.
1c7f51c75a x86_64: Fix asm constraints in feraiseexcept (bug 30305)
8d07e65d15 gshadow: Matching sgetsgent, sgetsgent_r ERANGE handling (bug 30151)
b7cc55a24e x86: Check minimum/maximum of non_temporal_threshold [BZ #29953]
3f63f9dfe1 stdlib: Undo post review change to 16adc58e73f3 [BZ #27749]
757d9a6306 elf: Smoke-test ldconfig -p against system /etc/ld.so.cache
416bd20b3f Use 64-bit time_t interfaces in strftime and strptime (bug 30053)
ae045ed16b cdefs: Limit definition of fortification macros
6bcd5d8e36 x86: Prevent SIGSEGV in memcmp-sse2 when data is concurrently modified [BZ #29863]
82663d3c03 time: Set daylight to 1 for matching DST/offset change (bug 29951)
d9923235f0 elf/tst-tlsopt-powerpc fails when compiled with -mcpu=power10 (BZ# 29776)

Signed-off-by: Deepthi Hemraj <deepadeepthi98@gmail.com>
---
 meta/recipes-core/glibc/glibc-version.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-core/glibc/glibc-version.inc b/meta/recipes-core/glibc/glibc-version.inc
index d36da0ce3f..4d8d96cefb 100644
--- a/meta/recipes-core/glibc/glibc-version.inc
+++ b/meta/recipes-core/glibc/glibc-version.inc
@@ -1,6 +1,6 @@
 SRCBRANCH ?= "release/2.35/master"
 PV = "2.35"
-SRCREV_glibc ?= "293211b6fddf60fc407d21fcba0326dd2148f76b"
+SRCREV_glibc ?= "1c7f51c75ae300fe52ccb636e71b8e28cb20824c"
 SRCREV_localedef ?= "794da69788cbf9bf57b59a852f9f11307663fa87"
 
 GLIBC_GIT_URI ?= "git://sourceware.org/git/glibc.git"
-- 
2.34.1



             reply	other threads:[~2023-04-28  8:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-28  8:29 Deepthi Hemraj [this message]
2023-04-28  8:43 ` [kirkstone][PATCH] glibc: stable 2.35 branch updates Deepthi Hemraj
  -- strict thread matches above, loose matches on Subject: below --
2023-06-12  9:44 Deepthi Hemraj
2023-06-12  9:58 ` Deepthi.Hemraj
2023-06-12 10:00   ` Deepthi.Hemraj
2023-06-13  7:08   ` Deepthi.Hemraj
2023-06-13  7:09   ` Deepthi.Hemraj
2023-09-13 11:18 Sanjana
2023-09-13 11:30 ` Sanjana V
2024-05-30  5:17 Deepthi.Hemraj
2024-05-30 15:57 ` Hemraj, Deepthi
2024-09-25 13:11 Deepthi.Hemraj
2024-09-25 13:16 ` Hemraj, Deepthi
2024-09-25 15:17 [OE-core] " Khem Raj
2024-09-26  5:34 ` Hemraj, Deepthi
2024-09-27 12:56 [OE-core] " Steve Sakoman
2024-10-03 11:22 ` Hemraj, Deepthi
2025-01-30  8:54 Deepesh.Varatharajan
2025-05-09  4:30 Deepesh.Varatharajan
2025-07-24  7:56 Deepesh.Varatharajan
2025-10-06 12:51 Deepesh.Varatharajan
2026-01-25 16:16 [OE-core][kirkstone][PATCH] " Peter Marko
2026-02-23 21:14 ` [kirkstone][PATCH] " Colin McAllister

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=20230428082947.4091975-1-deepadeepthi98@gmail.com \
    --to=deepadeepthi98@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