linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Cc: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>,
	linux-kernel@vger.kernel.org,
	Dongsoo Nathaniel Kim <dongsoo.kim@gmail.com>
Subject: Re: [PATCH] perf kvm: fix segfault by initializing file_name to NULL
Date: Thu, 28 Feb 2013 08:19:09 -0700	[thread overview]
Message-ID: <512F756D.90101@gmail.com> (raw)
In-Reply-To: <20130228142411.GE2656@ghostprotocols.net>

On 2/28/13 7:24 AM, Arnaldo Carvalho de Melo wrote:
> Just fast forwarded my perf/urgent to tip/perf/urgent, checked and the
> fix is there as pointed out by Xiao.

hmm.... hanging out in your perf/core branch rather than perf/urgent.

David

      reply	other threads:[~2013-02-28 15:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-28  3:29 [PATCH] perf kvm: fix segfault by initializing file_name to NULL David Ahern
2013-02-28  4:31 ` Xiao Guangrong
2013-02-28  4:43   ` David Ahern
2013-02-28 14:24     ` Arnaldo Carvalho de Melo
2013-02-28 15:19       ` David Ahern [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=512F756D.90101@gmail.com \
    --to=dsahern@gmail.com \
    --cc=acme@ghostprotocols.net \
    --cc=dongsoo.kim@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xiaoguangrong@linux.vnet.ibm.com \
    /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;
as well as URLs for NNTP newsgroup(s).