All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Cc: McClintock Matthew-B29882 <B29882@freescale.com>,
	St John Robert-RAT173 <RAT173@freescale.com>,
	Luo Zhenhua-B19537 <B19537@freescale.com>
Subject: Re: valgrind: fix debug info reading error when do memcheck on ppc targets
Date: Thu, 13 Sep 2012 10:52:51 +0100	[thread overview]
Message-ID: <1480210.p3lKEl3Cij@helios> (raw)
In-Reply-To: <CA452391058F6D4E9715FB2C29D9312A012B7381@039-SN2MPN1-022.039d.mgd.msft.net>

On Wednesday 12 September 2012 07:50:23 Luo Zhenhua-B19537 wrote:
> > -----Original Message-----
> > From: McClintock Matthew-B29882
> > Sent: Wednesday, September 12, 2012 12:03 PM
> > 
> > > diff --git
> > > a/meta/recipes-devtools/valgrind/valgrind-3.7.0/valgrind-3.7.0-fix-err
> > > or-of-reading-debug-info.patch
> > > b/meta/recipes-devtools/valgrind/valgrind-3.7.0/valgrind-3.7.0-fix-err
> > > or-of-reading-debug-info.patch
> > 
> > Patch needs Upstream-Status:
> [Luo Zhenhua-B19537] should the status be Pending if the patch has not been
> sent to upstream?

If the patch is suitable for sending upstream, yes.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



      reply	other threads:[~2012-09-13 10:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-12  3:44 valgrind: fix debug info reading error when do memcheck on ppc targets b19537
2012-09-12  4:02 ` McClintock Matthew-B29882
2012-09-12  4:11   ` Saul Wold
2012-09-12  7:50   ` Luo Zhenhua-B19537
2012-09-13  9:52     ` Paul Eggleton [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=1480210.p3lKEl3Cij@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=B19537@freescale.com \
    --cc=B29882@freescale.com \
    --cc=RAT173@freescale.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.