From: Steven Rostedt <srostedt@redhat.com>
To: Dhaval Giani <dhaval@linux.vnet.ibm.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: ftrace causing panics.
Date: Wed, 20 Feb 2008 10:42:32 -0500 [thread overview]
Message-ID: <47BC4A68.5050704@redhat.com> (raw)
In-Reply-To: <20080220152815.GB1082@linux.vnet.ibm.com>
Dhaval Giani wrote:
> sched-devel as of yesterday. (I don't think anything new has gone in
> today).
I just sent Ingo my fixes a few minutes ago. You may want to keep an I
out on updates to sched-devel.
>
> [sorry, not had enough time to get to the bottom of this the last few
> days]
>
No prob.
-- Steve
next prev parent reply other threads:[~2008-02-20 15:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080219124222.GB13780@linux.vnet.ibm.com>
[not found] ` <20080219140352.GB9965@elte.hu>
[not found] ` <20080219155433.GA4754@linux.vnet.ibm.com>
[not found] ` <20080219161608.GA1347@elte.hu>
2008-02-19 17:38 ` ftrace causing panics Dhaval Giani
2008-02-20 15:02 ` Steven Rostedt
2008-02-20 15:28 ` Dhaval Giani
2008-02-20 15:42 ` Steven Rostedt [this message]
2008-02-20 15:46 ` Ingo Molnar
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=47BC4A68.5050704@redhat.com \
--to=srostedt@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=dhaval@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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.