All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: sundeep.kokkonda@windriver.com
Cc: openembedded-core@lists.openembedded.org,
	randy.macleod@windriver.com, naveen.gowda@windriver.com,
	shivaprasad.moodalappa@windriver.com, yash.shinde@windriver.com,
	deepthi.hemraj@windriver.com, umesh.kallapa@windriver.com,
	steve@sakoman.com
Subject: Re: [OE-core] [PATCH] glibc: stable 2.38 branch updates
Date: Mon, 27 Nov 2023 20:47:55 +0100	[thread overview]
Message-ID: <202311271947555ac0c342@mail.local> (raw)
In-Reply-To: <20231127040046.1024625-1-sundeep.kokkonda@windriver.com>

Please follow https://docs.yoctoproject.org/dev/contributor-guide/submit-changes.html#fixing-your-from-identity

On 26/11/2023 20:00:46-0800, Sundeep KOKKONDA via lists.openembedded.org wrote:
> Below commits on glibc-2.38 stable branch are updated.
> 1e04dcec49 Revert "elf: Move l_init_called_next to old place of l_text_end in link map"
> 719866ab2f Revert "elf: Always call destructors in reverse constructor order (bug 30785)"
> e0b6c9706c Revert "elf: Remove unused l_text_end field from struct link_map"
> 
> Signed-off-by: Sundeep KOKKONDA <sundeep.kokkonda@windriver.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 19b98bc11a..ccf9d505c5 100644
> --- a/meta/recipes-core/glibc/glibc-version.inc
> +++ b/meta/recipes-core/glibc/glibc-version.inc
> @@ -1,6 +1,6 @@
>  SRCBRANCH ?= "release/2.38/master"
>  PV = "2.38+git"
> -SRCREV_glibc ?= "750a45a783906a19591fb8ff6b7841470f1f5701"
> +SRCREV_glibc ?= "1e04dcec491bd8f48b5b74ce3e8414132578a645"
>  SRCREV_localedef ?= "e0eca29583b9e0f62645c4316ced93cf4e4e26e1"
>  
>  GLIBC_GIT_URI ?= "git://sourceware.org/git/glibc.git;protocol=https"
> -- 
> 2.42.0
> 

> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#191246): https://lists.openembedded.org/g/openembedded-core/message/191246
> Mute This Topic: https://lists.openembedded.org/mt/102823529/3617179
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [alexandre.belloni@bootlin.com]
> -=-=-=-=-=-=-=-=-=-=-=-
> 


-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


  parent reply	other threads:[~2023-11-27 19:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-27  4:00 [PATCH] glibc: stable 2.38 branch updates Sundeep KOKKONDA
2023-11-27  4:01 ` Sundeep KOKKONDA
2023-11-27  4:14 ` [OE-core] " Khem Raj
2023-11-27 19:47 ` Alexandre Belloni [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-09-27 10:12 [][PATCH] " Deepthi Hemraj
2023-09-28  1:36 ` [OE-core] " Khem Raj

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=202311271947555ac0c342@mail.local \
    --to=alexandre.belloni@bootlin.com \
    --cc=deepthi.hemraj@windriver.com \
    --cc=naveen.gowda@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=randy.macleod@windriver.com \
    --cc=shivaprasad.moodalappa@windriver.com \
    --cc=steve@sakoman.com \
    --cc=sundeep.kokkonda@windriver.com \
    --cc=umesh.kallapa@windriver.com \
    --cc=yash.shinde@windriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.