public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Olien <dmo@osdl.org>
To: Eyal Lebedinsky <eyal@eyal.emu.id.au>
Cc: Andrea Arcangeli <andrea@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.21pre2aa1: compile error in DAC960.c
Date: Mon, 30 Dec 2002 16:49:11 -0800	[thread overview]
Message-ID: <20021230164911.A12919@build.pdx.osdl.net> (raw)
In-Reply-To: <3E0A8685.5CAE1CE0@eyal.emu.id.au>; from eyal@eyal.emu.id.au on Thu, Dec 26, 2002 at 03:33:09PM +1100


I have a patch that works at the URL:

	http://www.osdl.org/archive/dmo/DAC960_2.4.20aa1/

I originally developed it for the aa1 patch.  But it works
on the newer aa patches as well.

On Thu, Dec 26, 2002 at 03:33:09PM +1100, Eyal Lebedinsky wrote:
> As is the case in the last few -aa patches, we still have the
> problem in drivers/block/DAC960.c.
> 
> I suggest that someone who knows fixes it, or else remove it
> from the -aa collection.
> 
> --
> Eyal Lebedinsky (eyal@eyal.emu.id.au) <http://samba.org/eyal/>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

  reply	other threads:[~2002-12-31  0:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-26  1:06 2.4.21pre2aa1 Andrea Arcangeli
2002-12-26  2:26 ` 2.4.21pre2aa1 Eyal Lebedinsky
2002-12-26  4:22 ` 2.4.21pre2aa1: compile error in fs/buffer.c Eyal Lebedinsky
2002-12-26  4:33 ` 2.4.21pre2aa1: compile error in DAC960.c Eyal Lebedinsky
2002-12-31  0:49   ` Dave Olien [this message]
2003-01-07 19:38     ` Andrea Arcangeli
2002-12-26 15:13 ` 2.4.21pre2aa1 J.A. Magallón
2002-12-26 15:26   ` 2.4.21pre2aa1 Marc-Christian Petersen
2002-12-31 11:25     ` 2.4.21pre2aa1 J.A. Magallon

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=20021230164911.A12919@build.pdx.osdl.net \
    --to=dmo@osdl.org \
    --cc=andrea@suse.de \
    --cc=eyal@eyal.emu.id.au \
    --cc=linux-kernel@vger.kernel.org \
    /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