From: Zhixiong Chi <zhixiong.chi@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] glibc: malloc: Add missing arena lock in malloc_info
Date: Fri, 24 Nov 2017 12:32:54 +0800 [thread overview]
Message-ID: <5A17A0F6.9090904@windriver.com> (raw)
In-Reply-To: <CAJTo0LbAMCEPOwE9SHNbtuGuO=63GHP8wYh3O9jG27U3xJKNAA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 945 bytes --]
Hi Ross,
Is your meaning that I regenerate this patch based on
poky-contrib:ross/mut2 branch?
Thanks.
On 2017年11月23日 19:58, Burton, Ross wrote:
> Thanks Andre. There's a glibc 2.26 upgrade pending and this doesn't
> apply on top of that, can you rebase? poky-contrib:ross/mut2 is where
> I'm staging the toolchain updates.
>
> Ross
>
> On 22 November 2017 at 00:50, Andre McCurdy <armccurdy@gmail.com
> <mailto:armccurdy@gmail.com>> wrote:
>
> On Tue, Nov 21, 2017 at 3:05 PM, Burton, Ross
> <ross.burton@intel.com <mailto:ross.burton@intel.com>> wrote:
> > What glibc release is this in? We've an upgrade patch pending
> that bumps it
> > to 77f921dac17c5fa99bd9e926d926c327982895f7.
>
> It's currently in the glibc master branch only (ie hasn't been
> backported to the 2.26 release branch).
>
>
--
---------------------
Thanks,
Zhixiong Chi
Tel: +86-10-8477-7036
[-- Attachment #2: Type: text/html, Size: 2154 bytes --]
next prev parent reply other threads:[~2017-11-24 4:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-20 7:44 [PATCH] glibc: malloc: Add missing arena lock in malloc_info Zhixiong Chi
2017-11-21 5:52 ` Khem Raj
2017-11-21 23:05 ` Burton, Ross
2017-11-22 0:50 ` Andre McCurdy
2017-11-23 11:58 ` Burton, Ross
2017-11-24 4:32 ` Zhixiong Chi [this message]
2017-11-24 15:29 ` Burton, Ross
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=5A17A0F6.9090904@windriver.com \
--to=zhixiong.chi@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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