From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] valgrind: bump to version 3.9.0
Date: Tue, 28 Jan 2014 18:39:19 +0100 [thread overview]
Message-ID: <20140128183919.186508cf@skate> (raw)
In-Reply-To: <1388680480-58533-1-git-send-email-jezz@sysmic.org>
Hello,
On Thu, 2 Jan 2014 17:34:40 +0100, J?r?me Pouiller wrote:
> -VALGRIND_VERSION = 3.8.1
> +VALGRIND_VERSION = 3.9.0
> VALGRIND_SITE = http://valgrind.org/downloads/
> VALGRIND_SOURCE = valgrind-$(VALGRIND_VERSION).tar.bz2
> VALGRIND_LICENSE = GPLv2 GFDLv1.2
One of the new features of Valgrind 3.9.0 is the addition of MIPS
support. Maybe it would be good to enable Valgrind on these
architectures. I'm adding Vincente and Markos in the Cc list, since
they are our main MIPS contributors. They might probably be interested
in doing this work, after testing on MIPS hardware.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-01-28 17:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-02 16:34 [Buildroot] [PATCH v2] valgrind: bump to version 3.9.0 Jérôme Pouiller
2014-01-04 22:40 ` Peter Korsgaard
2014-01-28 17:39 ` Thomas Petazzoni [this message]
2014-01-29 9:44 ` Markos Chandras
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=20140128183919.186508cf@skate \
--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