public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Doug Ledford <dledford@redhat.com>
To: Neale Banks <neale@lowendale.com.au>
Cc: linux-kernel@vger.kernel.org, Alan Cox <alan@redhat.com>
Subject: Re: [PATCH] i810 driver update.
Date: Mon, 28 Jan 2002 21:47:15 -0500	[thread overview]
Message-ID: <3C560D33.5020608@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.05.10201291348590.1513-100000@marina.lowendale.com.au>

Neale Banks wrote:
> On Mon, 28 Jan 2002, Doug Ledford wrote:
> 
> [...]
> 
>>>Are the fixes in this going to be applicable to 2.2 also (FWIW, 2.2's
>>>i810_audio #defines ``DRIVER_VERSION "0.17"'')?
>>>
>>
>>I'm sure the fixes are relevant.  How well they may integrate into 2.2 is 
>>another question :-/
>>
> 
> Indeed ;-)  Alan?
> [...]
> 
>>The best I can do it to make a diff between the 0.17 driver version I have 
>>here and the 0.21 driver version.  Maybe that incremental diff will apply to 
>>the 2.2 kernel's i810_audio.c and bring it up to date without any specific 
>>back port needed.  It's attached.
>>
> 
> Thanks anyway, but it doesn't look too hopeful (patch complaints
> appended).  I suspect your "0.17" and 2.2's "0.17" may not be the same
> thing (in 2.2.21pre2 i810_audio.c is 51877 bytes and "sum (GNU textutils)  
> 2.0" reports "44467 51"
> 
> Regards,
> Neale.
> 
> $ patch --dry-run < 2.2-i810.patch 
> patching file `i810_audio.c.17'
> Hunk #1 succeeded at 181 (offset -25 lines).
> Hunk #2 FAILED at 576.
> Hunk #3 FAILED at 653.
> Hunk #4 FAILED at 1107.
> Hunk #5 FAILED at 1117.
> Hunk #6 FAILED at 1138.
> Hunk #7 FAILED at 1169.
> Hunk #8 succeeded at 1127 with fuzz 1 (offset -248 lines).
> Hunk #9 FAILED at 1278.
> Hunk #10 FAILED at 1492.
> Hunk #11 FAILED at 2175.
> Hunk #12 FAILED at 2877.
> 10 out of 12 hunks FAILED -- saving rejects to i810_audio.c.17.rej
> 
> 

Yeah, there's a vast difference there.  I would guess that the difference is 
the presence of S/PDIF support in the 2.4+ .17 driver version and none in 
the 2.2 version.  Email me the whole 0.17 file you have there (off-list) and 
I'll see about integrating the changes.


-- 

  Doug Ledford <dledford@redhat.com>  http://people.redhat.com/dledford
       Please check my web site for aic7xxx updates/answers before
                       e-mailing me about problems


  reply	other threads:[~2002-01-29  2:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-28 22:26 [PATCH] i810 driver update Doug Ledford
2002-01-29  1:39 ` Neale Banks
2002-01-29  2:07   ` Doug Ledford
2002-01-29  2:55     ` Neale Banks
2002-01-29  2:47       ` Doug Ledford [this message]
2002-01-29  6:18 ` Graeme Read
2002-01-29  6:20   ` bogus imode? Joe Wong
  -- strict thread matches above, loose matches on Subject: below --
2002-01-28 22:28 [PATCH] i810 driver update Doug Ledford
     [not found] <Pine.LNX.4.05.10201291422170.1513-200000@marina.lowendale.com.au>
2002-01-29  3:28 ` Doug Ledford

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=3C560D33.5020608@redhat.com \
    --to=dledford@redhat.com \
    --cc=alan@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neale@lowendale.com.au \
    /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