From: Lin Tong <tong.lin@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] [PULL] valgrind:fix bug 1129 for supporting kernel 3.0
Date: Tue, 9 Aug 2011 16:30:49 +0800 [thread overview]
Message-ID: <cover.1312869726.git.tong.lin@intel.com> (raw)
Hi Saul,
This pull request adds 3.0 kernel supports in valgrind's configure.in, which fixed bug 1129. Please help to review and pull.
[YOCTO #1129]
Thanks,
Tong
The following changes since commit 19252e0592c59ed0fb06ca510d11e564518f746d:
Nitin A Kamble (1):
x86 tune inc files: add x32 abi tune parameters
are available in the git repository at:
git://git.pokylinux.org/poky-contrib tlin100/bug1129
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=tlin100/bug1129
Lin Tong (1):
valgrind: supporting Linux kernel 3.0
.../valgrind-3.6.1/fix_3.0_kernel_support.patch | 26 ++++++++++++++++++++
meta/recipes-devtools/valgrind/valgrind_3.6.1.bb | 3 +-
2 files changed, 28 insertions(+), 1 deletions(-)
create mode 100644 meta/recipes-devtools/valgrind/valgrind-3.6.1/fix_3.0_kernel_support.patch
next reply other threads:[~2011-08-09 8:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-09 8:30 Lin Tong [this message]
2011-08-09 8:30 ` [PATCH 1/1] valgrind: supporting Linux kernel 3.0 Lin Tong
2011-08-09 8:26 ` Koen Kooi
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=cover.1312869726.git.tong.lin@intel.com \
--to=tong.lin@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.