From: Masami Hiramatsu <mhiramat@redhat.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
ananth@in.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: [BUGFIX][ PATCH] kprobes: fix kprobe selftest configuration dependency
Date: Wed, 01 Jul 2009 08:02:33 -0400 [thread overview]
Message-ID: <4A4B5059.2000805@redhat.com> (raw)
In-Reply-To: <20090701084304.GC8171@elte.hu>
On 2009年07月01日 04:43, Ingo Molnar wrote:
> * Masami Hiramatsu <mhiramat@redhat.com> wrote:
>
>> Masami Hiramatsu wrote:
>>> Ingo Molnar wrote:
>>>> * Masami Hiramatsu <mhiramat@redhat.com> wrote:
>>>>
>>>>> Oops, I couldn't reproduce this bug on the latest -tip tree.
>>>> maybe because i applied your fix already? ;-)
>>> If so, I'll be happy. But I reverted that change and checked :-(
>>> Maybe, that came from a combination of configs (but I've lost it...)
>> Ok, I found.
>> Sorry, the problem has been fixed with below commit...
>>
>> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=ac6ca5c86c63dd95acc6a34dff8d33c23b703a37
>
> thx - i thus dropped this:
>
> 130c5b2 kprobes: Fix kprobe selftest configuration dependency
>
> Kept the other two patches - one for tracing/urgent (for .31), the
> other for tracing/core (.32). Agreed?
Yes, I agreed. :-)
Thanks!
--
Masami Hiramatsu
Software Engineer
Hitachi Computer Products (America), Inc.
Software Solutions Division
e-mail: mhiramat@redhat.com
prev parent reply other threads:[~2009-07-01 12:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-22 21:03 [BUGFIX][ PATCH] kprobes: fix kprobe selftest configuration dependency Masami Hiramatsu
2009-06-30 21:38 ` Andrew Morton
2009-06-30 21:41 ` Linus Torvalds
2009-06-30 22:11 ` Masami Hiramatsu
2009-06-30 23:19 ` Masami Hiramatsu
2009-06-30 23:23 ` Ingo Molnar
2009-06-30 23:48 ` Masami Hiramatsu
2009-07-01 0:09 ` Masami Hiramatsu
2009-07-01 8:43 ` Ingo Molnar
2009-07-01 12:02 ` Masami Hiramatsu [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=4A4B5059.2000805@redhat.com \
--to=mhiramat@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=ananth@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 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.