From: Alexey Starikovskiy <alexey_y_starikovskiy@linux.intel.com>
To: Dave Jones <davej@redhat.com>
Cc: cpufreq@lists.linux.org.uk
Subject: Re: [PATCH 1/8] acpi-cpufreq: fix multicore bug
Date: Tue, 01 Aug 2006 11:58:51 +0400 [thread overview]
Message-ID: <44CF09BB.7020605@linux.intel.com> (raw)
In-Reply-To: <20060731214950.GD31513@redhat.com>
Dave Jones wrote:
> On Mon, Jul 31, 2006 at 10:38:03PM +0400, Alexey Starikovskiy wrote:
> > acpi-cpufreq.c | 98
> > +++++++++------------------------------------------------
> > 1 file changed, 17 insertions(+), 81 deletions(-)
> >
> > Fix a problem on a multicore processors.
> >
> > Signed-off: Denis Sadykov <denis.m.sadykov@intel.com>
> > Signed-off-by: Venkatesh Pallipadi <venkatesh.pallipadi at intel.com>
> > Signed-off-by: Alexey Starikovskiy <alexey.y.starikovskiy at intel.com>
>
> Can I get a little more verbose description for the changelog please ?
> I think I understand whats going on here, but I'd like to understand
> it more than "fix a bug" when I'm browsing the history 6 months from now.
This is a fix for broken BIOSes, which report processors as hardware independent by
not giving an optional _PSD object in CPU device. Without this patch we will not be
able to set same frequency on every other processor (although it is already
set by a shared state from first processor), so notifications will be missing.
> Also, is there any way you can make thunderbird not send mails
> with format=flowed in your Content-type: ? mutt respects this attribute
> and handily word-wraps your diffs. (Which doesn't matter for applying
> them, but it does make it a pain when reviewing).
Set row width to fixed 80, don't know if it helps...
Thanks,
Alex.
prev parent reply other threads:[~2006-08-01 7:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-31 18:38 [PATCH 1/8] acpi-cpufreq: fix multicore bug Alexey Starikovskiy
2006-07-31 21:49 ` Dave Jones
2006-08-01 7:58 ` Alexey Starikovskiy [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=44CF09BB.7020605@linux.intel.com \
--to=alexey_y_starikovskiy@linux.intel.com \
--cc=cpufreq@lists.linux.org.uk \
--cc=davej@redhat.com \
/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