From: Andi Kleen <andi@firstfloor.org>
To: Soumendu Satapathy <satapathy.soumendu@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Oops in 2.6.27.39 with latest DTrace linux port
Date: Tue, 22 Dec 2009 21:45:43 +0100 [thread overview]
Message-ID: <87ljgud9fs.fsf@basil.nowhere.org> (raw)
In-Reply-To: <b3eb0ed40912221226o56e4de26oc3119f3b0a946548@mail.gmail.com> (Soumendu Satapathy's message of "Tue, 22 Dec 2009 15:26:11 -0500")
Soumendu Satapathy <satapathy.soumendu@gmail.com> writes:
> Hi,
>
> http://lkml.org/lkml/2009/12/22/219
>
> Attaching the patch for the above:-
You need to send that to the dtrace for linux author,
strace is not in the mainline sources.
You could also encourage him/her to submit his patches for
review.
-Andi
next prev parent reply other threads:[~2009-12-22 20:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-22 20:26 Oops in 2.6.27.39 with latest DTrace linux port Soumendu Satapathy
2009-12-22 20:45 ` Andi Kleen [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-12-22 20:42 Oops in 2.6.27.39 with Latest " Soumendu Satapathy
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=87ljgud9fs.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=satapathy.soumendu@gmail.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