[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4766A199.70504@redhat.com>
Date: Mon, 17 Dec 2007 11:19:37 -0500
From: Masami Hiramatsu <mhiramat@...hat.com>
To: Ingo Molnar <mingo@...e.hu>
CC: Harvey Harrison <harvey.harrison@...il.com>,
LKML <linux-kernel@...r.kernel.org>,
Prasanna S Panchamukhi <prasanna@...ibm.com>,
Ananth N Mavinakayanahalli <ananth@...ibm.com>,
Masami Hiramatsu <hiramatu@....hitachi.co.jp>,
Rusty Lynch <rusty.lynch@...el.com>,
Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
Keshavamurthy Anil S <anil.s.keshavamurthy@...el.com>
Subject: Re: Final kprobes rollup patches
Hi Ingo,
Ingo Molnar wrote:
> * Masami Hiramatsu <mhiramat@...hat.com> wrote:
>
>>> cool! Please Cc: lkml and Harvey as well so that there's less
>>> overlap in unification work - Harvey spent quite some time unifying
>>> and cleaning up the kprobes code during the past week.
>> Should I rewrite it based on current git tree?
>> My patch includes 3 part of patches.
>> - 2 Bugfix patches (which is not merged yet.)
>> - 2 booster patches (ditto)
>> - 2 unification patches (most of this patches are already done by Harvey's patch)
>
> would it be easier/more robust to first did the unification patches and
> then get the bugfixes and new features in? That would give us your
> bugfixes and new features on both 32-bit and 64-bit at the same time.
As far as I can see, my patches have less #ifdefs than Harvey's.
However, that patch's granularity may be not so good currently.
> feel free to do whichever approach you prefer - but it would be nice to
> preserve the unification and cleanup work done by Harvey.
OK, rewriting will take a while, so I sent a series of patches which I have just now.
> btw., is any of your bugfixes 2.6.24 material?
Yes, I'd like to fix first two bugs in 2.6.24.
Thank you very much,
>
> Ingo
--
Masami Hiramatsu
Software Engineer
Hitachi Computer Products (America) Inc.
Software Solutions Division
e-mail: mhiramat@...hat.com, masami.hiramatsu.pt@...achi.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists