From: "Mittal, Anuj" <anuj.mittal@intel.com>
To: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>,
"pgowda.cve@gmail.com" <pgowda.cve@gmail.com>
Cc: "rwmacleod@gmail.com" <rwmacleod@gmail.com>,
"umesh.kalappa0@gmail.com" <umesh.kalappa0@gmail.com>
Subject: Re: [hardknott][PATCH] glibc: upgrade glibc-2.33 to latest version
Date: Mon, 14 Feb 2022 08:26:23 +0000 [thread overview]
Message-ID: <598913e85781eee1989a7116c8c91747a14d5171.camel@intel.com> (raw)
In-Reply-To: <CALY4984r-NMcFLM1tEO4ZhrySxve6Ye5Nxq7HCq5ufVaQYj6Hw@mail.gmail.com>
On Mon, 2022-02-14 at 13:08 +0530, pgowda cve wrote:
> Gentle Ping on this patch.
I didn't realize this is separate from the glibc upgrade sent earlier.
I will include it now.
Thanks,
Anuj
>
> On Sun, Jan 30, 2022 at 11:50 AM pgowda <pgowda.cve@gmail.com> wrote:
> >
> > glibc-2.33 has been upgraded to latest version that includes many
> > CVE and
> > other bug fixes. Ran the regressions and results are better.
> >
> > Signed-off-by: pgowda <pgowda.cve@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 63241ee951..e1eefdee49 100644
> > --- a/meta/recipes-core/glibc/glibc-version.inc
> > +++ b/meta/recipes-core/glibc/glibc-version.inc
> > @@ -1,6 +1,6 @@
> > SRCBRANCH ?= "release/2.33/master"
> > PV = "2.33"
> > -SRCREV_glibc ?= "55b99e9ed07688019609bd4dcd17d3ebf4572948"
> > +SRCREV_glibc ?= "3e2a15c666e40e5ee740e5079c56d83469280323"
> > SRCREV_localedef ?= "bd644c9e6f3e20c5504da1488448173c69c56c28"
> >
> > GLIBC_GIT_URI ?= "git://sourceware.org/git/glibc.git"
> > --
> > 2.31.1
> >
next prev parent reply other threads:[~2022-02-14 8:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-30 6:20 [hardknott][PATCH] glibc: upgrade glibc-2.33 to latest version pgowda
2022-02-14 7:38 ` pgowda cve
2022-02-14 8:26 ` Mittal, Anuj [this message]
2022-04-20 14:35 ` [OE-core] " Randy MacLeod
2022-04-20 15:30 ` pgowda cve
2022-04-20 15:41 ` Randy MacLeod
2022-04-20 16:14 ` pgowda cve
2022-04-20 16:53 ` Randy MacLeod
2022-04-20 23:18 ` Mittal, Anuj
-- strict thread matches above, loose matches on Subject: below --
2021-10-17 2:51 Pgowda
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=598913e85781eee1989a7116c8c91747a14d5171.camel@intel.com \
--to=anuj.mittal@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=pgowda.cve@gmail.com \
--cc=rwmacleod@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;
as well as URLs for NNTP newsgroup(s).