From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: "平松雅巳 / HIRAMATU，MASAMI" <masami.hiramatsu.pt@hitachi.com>
Cc: Namhyung Kim <namhyung@kernel.org>,
"linux-perf-users@vger.kernel.org"
<linux-perf-users@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Milian Wolff <milian.wolff@kdab.com>
Subject: Re: [PATCH perf/core ] [BUGFIX] perf probe: Fix a segfault when removing uprobe events
Date: Fri, 18 Sep 2015 11:31:43 -0300 [thread overview]
Message-ID: <20150918143143.GR11551@kernel.org> (raw)
In-Reply-To: <20150918142830.GQ11551@kernel.org>
Em Fri, Sep 18, 2015 at 11:28:30AM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Fri, Sep 18, 2015 at 11:26:22AM -0300, Arnaldo Carvalho de Melo escreveu:
> > Em Fri, Sep 18, 2015 at 01:39:13AM +0000, 平松雅巳 / HIRAMATU，MASAMI escreveu:
> > > Could you pull this bugfix as an urgent patch, since this fixes a critical
> > > problem?
> > Sure, thanks for the reminder.
> But it is not applying, checking:
> [acme@zoo linux]$ patch -p1 < /wb/1.patch
> patching file tools/perf/builtin-probe.c
> Hunk #1 FAILED at 380.
> 1 out of 1 hunk FAILED -- saving rejects to file tools/perf/builtin-probe.c.rej
> [acme@zoo linux]$
The way you reported made me somehow think this was for perf/urgent, but
the function it patches is not even there, ok, applying to perf/core.
Applied.
- Arnaldo
next prev parent reply other threads:[~2015-09-18 14:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 12:52 [PATCH perf/core ] [BUGFIX] perf probe: Fix a segfault when removing uprobe events Masami Hiramatsu
2015-09-18 1:39 ` 平松雅巳 / HIRAMATU，MASAMI
2015-09-18 1:39 ` 平松雅巳 / HIRAMATU，MASAMI
2015-09-18 14:26 ` Arnaldo Carvalho de Melo
2015-09-18 14:28 ` Arnaldo Carvalho de Melo
2015-09-18 14:31 ` Arnaldo Carvalho de Melo [this message]
2015-09-18 21:24 ` Paul Clarke
2015-09-23 8:43 ` [tip:perf/core] " tip-bot for Masami Hiramatsu
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=20150918143143.GR11551@kernel.org \
--to=acme@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=milian.wolff@kdab.com \
--cc=namhyung@kernel.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.