From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] jemalloc: add a check for valgrind being configured as well
Date: Sun, 11 Sep 2016 22:27:29 +0200 [thread overview]
Message-ID: <20160911222729.36d49c29@free-electrons.com> (raw)
In-Reply-To: <1473378120-7549-1-git-send-email-ckhardin@exablox.com>
Hello,
On Thu, 8 Sep 2016 16:42:00 -0700, Charles Hardin wrote:
> jemalloc can be compiled with valgrind support being enabled
> to produce proper output, so when the valgrind package has
> been configured configure jemalloc appropriately.
>
> Signed-off-by: Charles Hardin <ckhardin@exablox.com>
> ---
> package/jemalloc/jemalloc.mk | 9 +++++++++
> 1 file changed, 9 insertions(+)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-09-11 20:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-08 23:42 [Buildroot] [PATCH 1/1] jemalloc: add a check for valgrind being configured as well Charles Hardin
2016-09-11 20:27 ` Thomas Petazzoni [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=20160911222729.36d49c29@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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