From: Stephan Diestelhorst <langer_mann@web.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andi Kleen <andi@firstfloor.org>,
davej@codemonkey.org.uk, cpufreq@lists.linux.org.uk,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] Speedfreq-SMI call clobbers ECX
Date: Wed, 12 Mar 2008 16:04:04 +0100 [thread overview]
Message-ID: <200803121604.05065.langer_mann@web.de> (raw)
In-Reply-To: <20080311093903.GS25110@elte.hu>
Ingo Molnar wrote:
>
> I've applied your patch to x86.git.
Many thanks!
> Do you think it's 2.6.25 material? I'm inclined to have it in
> the 2.6.26 bucket. We could do your first, minimal fix in 2.6.25 and do
> this second, full fix in 2.6.26.
I am not familiar with the policies regarding the time-frame for
inclusion. So I guess the decision is up to you. I feel that the
changes are fairly small (at least for the first patch) so perhaps
splitting the release as you suggested allows people to get more
confidence in the larger patches with the clobbers and manual ebp
push/pop.
Doing this one step after the other has the additional benefit of
havinga fix for the core problem in fairly soon, so I can continue
using prebuilt distro kernels again, soon. :-) ( I know. I'm just lazy
sometimes. )
Apart from that: Feel free to do as you like, after all this code is
GPL.
Kind regards,
Stephan
prev parent reply other threads:[~2008-03-12 15:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-05 14:59 [PATCH 1/1] Speedfreq-SMI call clobbers ECX Stephan Diestelhorst
2008-03-05 15:35 ` Ingo Molnar
2008-03-05 16:02 ` H. Peter Anvin
2008-03-06 8:38 ` Stephan Diestelhorst
2008-03-06 8:51 ` Stephan Diestelhorst
2008-03-06 10:56 ` Ingo Molnar
2008-03-10 15:05 ` Stephan Diestelhorst
2008-03-10 16:46 ` Andi Kleen
2008-03-10 21:26 ` Stephan Diestelhorst
2008-03-10 21:51 ` Andi Kleen
2008-03-10 23:14 ` Stephan Diestelhorst
2008-03-11 9:39 ` Ingo Molnar
2008-03-12 15:04 ` Stephan Diestelhorst [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=200803121604.05065.langer_mann@web.de \
--to=langer_mann@web.de \
--cc=andi@firstfloor.org \
--cc=cpufreq@lists.linux.org.uk \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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