public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hugo Vanwoerkom <rociobarroso@att.net.mx>
To: Chris Wedgwood <cw@f00f.org>
Cc: ocilent1 <ocilent1@gmail.com>, Lee Revell <rlrevell@joe-job.com>,
	Con Kolivas <kernel@kolivas.org>,
	ck@vds.kolivas.org, linux list <linux-kernel@vger.kernel.org>,
	dsd@gentoo.org
Subject: Re: sound skips on 2.6.16.17
Date: Wed, 19 Jul 2006 08:47:20 -0500	[thread overview]
Message-ID: <44BE37E8.2040706@att.net.mx> (raw)
In-Reply-To: <20060719063344.GA1677@tuatara.stupidest.org>

Chris Wedgwood wrote:
> On Wed, Jul 19, 2006 at 02:03:25PM +0800, ocilent1 wrote:
>
>   
>> Hows progress on this bug? Don't suppose we have got an official fix
>> for this somewhere on the horizon?
>>     
>
> Daniel Drake posted this recently, I've not had a chance to look over
> it in detail but it's probably the best tested suggestion thus far.
>
> Does it work for you?
>
>
>   
<snip>

I tried that on 2.6.17-ck1 with good results:

...
patching file drivers/pci/quirks.c
Hunk #1 succeeded at 638 (offset -10 lines).
Hunk #2 succeeded at 678 (offset -10 lines).
...

Regards,

Hugo

  parent reply	other threads:[~2006-07-19 13:48 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4487F942.3030601@att.net.mx>
     [not found] ` <200606161115.53716.ocilent1@gmail.com>
     [not found]   ` <4493D24D.2010902@att.net.mx>
2006-06-17 11:29     ` sound skips on 2.6.16.17 Con Kolivas
2006-06-18  2:41       ` Chris Wedgwood
2006-06-18  4:04         ` ocilent1
2006-06-18  4:40           ` Chris Wedgwood
2006-06-18  4:49             ` ocilent1
2006-06-18 11:11             ` Hugo Vanwoerkom
2006-06-18 13:35               ` karsten wiese
2006-06-19  3:54             ` ocilent1
2006-06-19 21:24               ` Lee Revell
2006-06-19 21:50                 ` Chris Wedgwood
2006-06-20 18:35                   ` Lee Revell
2006-06-20 19:36                     ` Chris Wedgwood
2006-06-24 14:08                       ` Jacek J
2006-06-27 22:25                       ` Lee Revell
2006-06-27 22:48                         ` Chris Wedgwood
2006-07-07 16:33                           ` Lee Revell
2006-07-07 17:00                             ` Chris Wedgwood
2006-07-07 18:00                               ` Lee Revell
2006-07-19  6:03                               ` ocilent1
2006-07-19  6:33                                 ` Chris Wedgwood
2006-07-19 11:25                                   ` ocilent1
2006-07-19 13:47                                   ` Hugo Vanwoerkom [this message]
2006-07-19 13:51                                     ` ocilent1
2006-10-07 21:39                                     ` sound skips on 2.6.18-ck1 Hugo Vanwoerkom
2006-10-07 21:56                                       ` Hugo Vanwoerkom
2006-10-08 16:18                                       ` Hugo Vanwoerkom
2006-10-08 17:19                                         ` [ck] " Andreas Mohr
2006-10-08 17:33                                           ` Daniel Drake
2006-06-18 11:06         ` sound skips on 2.6.16.17 Hugo Vanwoerkom
2006-06-18 13:10         ` Sergey Vlasov

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=44BE37E8.2040706@att.net.mx \
    --to=rociobarroso@att.net.mx \
    --cc=ck@vds.kolivas.org \
    --cc=cw@f00f.org \
    --cc=dsd@gentoo.org \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ocilent1@gmail.com \
    --cc=rlrevell@joe-job.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