From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1] valgrind: bump version to 3.12.0
Date: Wed, 26 Oct 2016 22:48:20 +0200 [thread overview]
Message-ID: <20161026224820.2699bcbe@free-electrons.com> (raw)
In-Reply-To: <7ecbae13-4b09-8e76-b3f4-4f48e808c4e4@imgtec.com>
Hello,
On Wed, 26 Oct 2016 12:18:04 +0100, Vicente Olivert Riera wrote:
> I have done a build test and it didn't fail, so it looks like those
> upstream missing parts are not needed.
Thanks for testing. In such a case, please reply with a formal
Tested-by, so that patchwork catches it and I notice that the patch has
at least been looked at by one person.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-10-26 20:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-25 21:29 [Buildroot] [PATCH v1] valgrind: bump version to 3.12.0 Peter Seiderer
2016-10-26 11:18 ` Vicente Olivert Riera
2016-10-26 20:48 ` Thomas Petazzoni [this message]
2016-10-26 20:47 ` Thomas Petazzoni
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=20161026224820.2699bcbe@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