From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Jack Mitchell <ml@communistcode.co.uk>
Cc: Jack Mitchell <jack.mitchell@dbbroadcast.co.uk>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] local.conf.sample: change valgrind support architecture comment
Date: Thu, 13 Sep 2012 13:21:04 +0100 [thread overview]
Message-ID: <2145007.czf2bJ2Tzi@helios> (raw)
In-Reply-To: <1347535204-25960-1-git-send-email-ml@communistcode.co.uk>
On Thursday 13 September 2012 12:20:04 Jack Mitchell wrote:
> From: Jack Mitchell <jack.mitchell@dbbroadcast.co.uk>
>
> The comment for debug-tools states valgrind will only be installed for x86
> targets. This is not true as valgrind now supports x86*, PPC* and ARMv7a;
> alter the comment to reflect this.
I have to say I think we can just drop this part of the comment entirely given
how wide the support is now.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-09-13 12:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-13 11:20 [PATCH] local.conf.sample: change valgrind support architecture comment Jack Mitchell
2012-09-13 12:21 ` Paul Eggleton [this message]
2012-09-13 12:27 ` [PATCHv2] " Jack Mitchell
2012-09-19 17:39 ` Saul Wold
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=2145007.czf2bJ2Tzi@helios \
--to=paul.eggleton@linux.intel.com \
--cc=jack.mitchell@dbbroadcast.co.uk \
--cc=ml@communistcode.co.uk \
--cc=openembedded-core@lists.openembedded.org \
/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