From: "Marko, Peter" <Peter.Marko@siemens.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: "openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>
Subject: RE: [oe] [meta-oe][PATCH] jemalloc: Update to tip of dev branch
Date: Tue, 16 Apr 2024 18:21:49 +0000 [thread overview]
Message-ID: <AS1PR10MB5697FE098477B557DBEA6F3EFD082@AS1PR10MB5697.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CAMKF1sqUbeRSXXP44HMJSgmvuN9aHdzyhGvxUEYArnf=1D-pOg@mail.gmail.com>
-----Original Message-----
From: Khem Raj <raj.khem@gmail.com>
Sent: Tuesday, April 16, 2024 19:57
To: Marko, Peter (ADV D EU SK BFS1) <Peter.Marko@siemens.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [oe] [meta-oe][PATCH] jemalloc: Update to tip of dev branch
> On Tue, Apr 16, 2024 at 5:43 AM Marko, Peter <Peter.Marko@siemens.com> wrote:
> >
> > Hello,
> >
> > Could we revert this patch together with related part of related commit?
> > https://git.openembedded.org/meta-openembedded/commit/?h=scarthgap&id=
> > 92bcaa8c1b5f7e2bdd607eafe59ea2d5799ba7d6
> >
> > Dev branch is unstable and not really suitable for new LTS release.
>
> Last few releases have come of dev branch, so it is mainstream AFAICT, secondly, this fixes otherwise failing ptests with older versions so unit test wise it should be more sound.
>
> Are there any other reasons you have in mind that we may not want it ?
No, I'm just verifying versions during upgrade to new LTS.
>
> >
> > Thanks for considering this.
> > Peter
prev parent reply other threads:[~2024-04-16 18:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 3:02 [meta-oe][PATCH] jemalloc: Update to tip of dev branch Khem Raj
2024-04-16 12:43 ` [oe] " Marko, Peter
2024-04-16 17:57 ` Khem Raj
2024-04-16 18:21 ` Marko, Peter [this message]
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=AS1PR10MB5697FE098477B557DBEA6F3EFD082@AS1PR10MB5697.EURPRD10.PROD.OUTLOOK.COM \
--to=peter.marko@siemens.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raj.khem@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 read-only IMAP folder(s) and NNTP newsgroup(s).