From: Thomas Gleixner <tglx@linutronix.de>
To: Daniel Walker <dwalker@mvista.com>
Cc: akpm@osdl.org, johnstul@us.ibm.com, mingo@elte.hu,
zippel@linux-m68k.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: + clocksource-increase-initcall-priority.patch added to -mm tree
Date: Mon, 09 Oct 2006 08:56:26 +0200 [thread overview]
Message-ID: <1160376987.5686.160.camel@localhost.localdomain> (raw)
In-Reply-To: <1160350543.3693.238.camel@c-67-180-230-165.hsd1.ca.comcast.net>
On Sun, 2006-10-08 at 16:35 -0700, Daniel Walker wrote:
> I think you know what your talking about, and I respect your opinion.. I
> think you have some points, that I will follow up on. However most of
> what your saying comes off to me like, "Reverse _all_ your changes!" ,
> "Makes this patch set go away for 2 months", and I don't understand
> where that is coming from.
I did nowhere say, that you should revert _ALL_ your changes ! If you
need 2 month to fixup the issues I pointed at , I can't help it.
tglx
prev parent reply other threads:[~2006-10-09 6:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200610070153.k971ren4020838@shell0.pdx.osdl.net>
2006-10-08 8:06 ` + clocksource-increase-initcall-priority.patch added to -mm tree Thomas Gleixner
2006-10-08 10:19 ` Thomas Gleixner
2006-10-08 14:50 ` Daniel Walker
2006-10-08 14:53 ` Thomas Gleixner
2006-10-08 15:45 ` Daniel Walker
2006-10-08 15:58 ` Thomas Gleixner
2006-10-08 16:18 ` Daniel Walker
2006-10-08 16:52 ` Thomas Gleixner
2006-10-08 17:17 ` Daniel Walker
2006-10-08 19:03 ` Thomas Gleixner
2006-10-08 20:39 ` Daniel Walker
2006-10-08 20:52 ` Thomas Gleixner
2006-10-08 21:15 ` Daniel Walker
2006-10-08 21:20 ` Thomas Gleixner
2006-10-08 21:31 ` Daniel Walker
2006-10-08 21:38 ` Thomas Gleixner
2006-10-08 22:13 ` Daniel Walker
2006-10-08 22:53 ` Thomas Gleixner
2006-10-08 23:35 ` Daniel Walker
2006-10-09 6:56 ` Thomas Gleixner [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=1160376987.5686.160.camel@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=akpm@osdl.org \
--cc=dwalker@mvista.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=zippel@linux-m68k.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.