cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Xavier Bachelot <xb_ml@kelkoo.net>
To: Dave Jones <davej@redhat.com>
Cc: cpufreq@lists.linux.org.uk
Subject: Re: Fix for longhaul deadlock ?
Date: Thu, 11 May 2006 10:49:00 +0200	[thread overview]
Message-ID: <4462FA7C.9060904@kelkoo.net> (raw)
In-Reply-To: <20060510234039.GD25646@redhat.com>

Dave Jones wrote:
> On Thu, May 11, 2006 at 01:22:27AM +0200, Xavier Bachelot wrote:
>  > Hi,
>  > 
>  > VIA recently pretended to have fixed the long-known longhaul bug. I've 
>  > diff'ed the longhaul.c file from kernel tree against their patched 
>  > version. Result is attached. I didn't tested it and I don't pretend to 
>  > understand what the patch does, but I though I just post it here in case 
>  > someone more knowledgeable could kindly take a look.
>  > For reference, here is the link to VIA site : 
>  > http://www.viaarena.com/default.aspx?PageID=420&OSID=30&CatID=2800
> 
> *sigh*, I've now seen three separate 'fixes' for this driver, all different,
> and all of them against some ancient version of the driver, which makes
> creating diffs painful.
> 
> I'm in the process of moving house, but once I'm moved into my new place,
> putting my via machines back in working order and getting this driver
> ship-shape again is pretty high on my todo list.
> 
> 		Dave
> 
Nice to know it's on your todo list :-) Count me as a beta tester, 
especially if you plan to push a kernel with longhaul fixes to rawhide. 
A follow-up on this thread or a note sent to cpufreq ml would be much 
appreciated, as I'm not tracking rawhide closely though.

Cheers,

Xavier

      reply	other threads:[~2006-05-11  8:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-10 23:22 Fix for longhaul deadlock ? Xavier Bachelot
2006-05-10 23:40 ` Dave Jones
2006-05-11  8:49   ` Xavier Bachelot [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=4462FA7C.9060904@kelkoo.net \
    --to=xb_ml@kelkoo.net \
    --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