From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] valgrind: rename ptrcheck to sgcheck like upstream
Date: Fri, 6 Mar 2015 17:34:44 +0100 [thread overview]
Message-ID: <20150306173444.05bec8e7@free-electrons.com> (raw)
In-Reply-To: <1425652337-25911-1-git-send-email-mike@mikebwilliams.com>
Dear Mike Williams,
On Fri, 6 Mar 2015 09:32:17 -0500, Mike Williams wrote:
> Signed-off-by: Mike Williams <mike@mikebwilliams.com>
> ---
> package/valgrind/Config.in | 6 +++---
> package/valgrind/valgrind.mk | 8 ++++----
> 2 files changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/package/valgrind/Config.in b/package/valgrind/Config.in
> index 558d5f0..d9116dd 100644
> --- a/package/valgrind/Config.in
> +++ b/package/valgrind/Config.in
> @@ -53,10 +53,10 @@ config BR2_PACKAGE_VALGRIND_DHAT
> help
> This option allows to install the DHAT tool
>
> -config BR2_PACKAGE_VALGRIND_PTRCHECK
> - bool "Ptrcheck: an experimental head, stack and global array overrun detector"
> +config BR2_PACKAGE_VALGRIND_SGCHECK
When renaming config options, we want to add the corresponding
Config.in.legacy handling. See the file named Config.in.legacy in the
top-level directory of Buildroot sources for details.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-03-06 16:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 14:32 [Buildroot] [PATCH] valgrind: rename ptrcheck to sgcheck like upstream Mike Williams
2015-03-06 16:34 ` Thomas Petazzoni [this message]
2015-03-06 17:18 ` Mike Williams
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=20150306173444.05bec8e7@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