From: Ingo Molnar <mingo@elte.hu>
To: Masami Hiramatsu <mhiramat@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
ananth@in.ibm.com, fche@redhat.com,
LKML <linux-kernel@vger.kernel.org>,
systemtap-ml <systemtap@sources.redhat.com>
Subject: Re: [BUGFIX] request for picking fee039a1 up (Re: fee039a1 and ccbeed3a dependency)
Date: Fri, 3 Apr 2009 19:21:57 +0200 [thread overview]
Message-ID: <20090403172157.GL19982@elte.hu> (raw)
In-Reply-To: <49D259BD.1010402@redhat.com>
* Masami Hiramatsu <mhiramat@redhat.com> wrote:
> Hi Linus,
>
> Since the commit ccbeed3a changed pt_regs, kretprobe has to be
> updated (which was done by commit fee039a1) too.
>
> Could you pick up the commit fee039a1 from Ingo's -tip tree or
> linux-next?
Yeah - i already sent the tracing tree to Linus which includes this
bit too.
Ingo
prev parent reply other threads:[~2009-04-03 17:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090331031822.GG6411@in.ibm.com>
2009-03-31 17:58 ` [BUGFIX] request for picking fee039a1 up (Re: fee039a1 and ccbeed3a dependency) Masami Hiramatsu
2009-04-03 17:21 ` Ingo Molnar [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=20090403172157.GL19982@elte.hu \
--to=mingo@elte.hu \
--cc=ananth@in.ibm.com \
--cc=fche@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@redhat.com \
--cc=systemtap@sources.redhat.com \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox