From: Zachary Amsden <zach@vmware.com>
To: Chris Wright <chrisw@sous-sol.org>
Cc: Andrew Morton <akpm@osdl.org>, Andi Kleen <ak@muc.de>,
virtualization@lists.osdl.org
Subject: Re: [PATCH 1/5] Skip timer works.patch
Date: Wed, 15 Nov 2006 00:21:00 -0800 [thread overview]
Message-ID: <455ACDEC.7010808@vmware.com> (raw)
In-Reply-To: <20061115080323.GK1397@sequoia.sous-sol.org>
Chris Wright wrote:
> * Andi Kleen (ak@muc.de) wrote:
>
>> On Mon, Oct 30, 2006 at 12:54:55PM -0800, Zachary Amsden wrote:
>>
>>> Andi Kleen wrote:
>>>
>>>> no_timer_check. But it's only there on x86-64 in mainline - although there
>>>> were some patches to add it to i386 too.
>>>>
>>>>
>>> I can rename to match the x86-64 name.
>>>
>> I will do that in my tree.
>>
>
> Looks like this one might have been lost. Here's the renamed version
> (it's against 2.6.19-rc5-mm2, which should have your tree in it).
>
> thanks,
> -chris
>
Thanks Chris, this is definitely a required patch for us.
I'm a little worried after seeing failures to apply and missed patches
that we could have other things missing from the upstream path. Is
there an easy way for us to look at diffs between the trees? Just a
diff on arch/i386 and include/asm-i386 would tell me wonders, no matter
how much extra activity has gone on there.
Namaste,
Zach
next prev parent reply other threads:[~2006-11-15 8:21 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-20 0:09 [PATCH 1/5] Skip timer works.patch Zachary Amsden
2006-10-27 14:56 ` Andi Kleen
2006-10-27 19:09 ` Zachary Amsden
2006-10-27 21:16 ` Andi Kleen
2006-10-30 20:54 ` Zachary Amsden
2006-10-30 22:50 ` Andi Kleen
2006-10-30 23:09 ` Zachary Amsden
2006-10-30 23:12 ` Andi Kleen
2006-10-30 23:24 ` Zachary Amsden
2006-10-30 23:50 ` Andi Kleen
2006-11-15 8:03 ` Chris Wright
2006-11-15 8:21 ` Zachary Amsden [this message]
2006-11-15 22:40 ` Chris Wright
2006-11-15 22:54 ` Chris Wright
2006-11-16 3:27 ` Andi Kleen
2006-11-16 3:37 ` Chris Wright
2006-11-16 3:37 ` Andi Kleen
2006-11-16 5:06 ` Andrew Morton
2006-11-16 6:13 ` Zachary Amsden
2006-11-16 7:23 ` Andi Kleen
2006-11-16 7:02 ` Andi Kleen
2006-11-16 7:16 ` Chris Wright
2006-11-16 8:26 ` Chris Wright
2006-11-16 10:28 ` Chris Wright
2006-11-16 13:16 ` Andi Kleen
2006-11-16 19:03 ` Chris Wright
2006-11-16 19:46 ` Andi Kleen
2006-11-16 20:24 ` Chris Wright
2006-11-17 4:47 ` Andi Kleen
2006-11-17 7:33 ` Chris Wright
2006-11-17 7:38 ` Andi Kleen
2006-11-16 22:53 ` Andrew Morton
2006-11-16 23:08 ` Zachary Amsden
2006-11-16 23:10 ` Chris Wright
2006-11-17 5:05 ` Andi Kleen
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=455ACDEC.7010808@vmware.com \
--to=zach@vmware.com \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=chrisw@sous-sol.org \
--cc=virtualization@lists.osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).