From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] [PULL] valgrind: fix bug 1129 for supporting kernel 3.x
Date: Mon, 15 Aug 2011 10:02:56 -0700 [thread overview]
Message-ID: <4E495140.6040808@linux.intel.com> (raw)
In-Reply-To: <cover.1313143473.git.tong.lin@intel.com>
On 08/12/2011 03:21 AM, Lin Tong wrote:
> Hi Saul,
>
> This pull requests to add 3.x 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 a92d56058b21913570bb17ae416c3b00afce055e:
> Kumar Gala (1):
> gnome-doc-utils: respect python-dir setting EXTRA_OECONF
>
> are available in the git repository at:
>
> git://git.pokylinux.org/poky-contrib tlin100/bug1129-v2
> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=tlin100/bug1129-v2
>
> Lin Tong (1):
> valgrind: supporting on Linux kernel 3.x
>
> .../valgrind-3.6.1/fix_unsupporting_kernel_3.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_unsupporting_kernel_3.patch
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
Merged into OE-Core
Thanks
Sau!
prev parent reply other threads:[~2011-08-15 17:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-12 10:21 [PATCH 0/1] [PULL] valgrind: fix bug 1129 for supporting kernel 3.x Lin Tong
2011-08-12 10:21 ` [PATCH 1/1] valgrind: supporting on Linux " Lin Tong
2011-08-15 17:02 ` Saul Wold [this message]
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=4E495140.6040808@linux.intel.com \
--to=sgw@linux.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.