mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Lang <david.lang@digitalinsight.com>
To: Jaco Kroon <jkroon@cs.up.ac.za>
Cc: Adrian Bunk <bunk@fs.tum.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.3 adaptec I2O will not compile
Date: Thu, 26 Feb 2004 00:08:59 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.58.0402260007460.994@dlang.diginsite.com> (raw)
In-Reply-To: <403DA7FC.1060507@cs.up.ac.za>

I received a post from Mark Salyzyn with a new driver that does compile,
he said that he has submitted the patches (I didn't get a chance to try
the new kernel yet, I expect to do that shortly and will report any
problems)

David Lang

 On Thu, 26 Feb 2004, Jaco
Kroon wrote:

> Date: Thu, 26 Feb 2004 00:02:04 -0800
> From: Jaco Kroon <jkroon@cs.up.ac.za>
> To: Adrian Bunk <bunk@fs.tum.de>
> Cc: David Lang <david.lang@digitalinsight.com>,
>      Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
> Subject: Re: 2.6.3 adaptec I2O will not compile
>
>
> Adrian Bunk wrote:
>
> >On Fri, Feb 20, 2004 at 01:52:24PM -0800, David Lang wrote:
> >
> >
> >>when attempting to compile in support for the adaptec 2100/3100 series
> >>Raid card I get the following errors. I have attached my config
> >>
> >>
> >>
> >
> >
> I am currently working on this, so far I've managed to sort out the irq
> problems and only have some dma stuff that does not compile.  I don't
> think I'm going to bother getting it to compile though and rather
> directly convert to the new DMA-mapping stuff.  If anyone has any
> pointers and tips and pitfalls I need to look out for, please don't
> hessitate to mail me (It will be greatly appreciated).
>
> Jaco
> --
> Once I finally figured out all of life's answers, they changed the
> questions.
> ===========================================
> This message and attachments are subject to a disclaimer. Please refer
> to www.it.up.ac.za/documentation/governance/disclaimer/ for full
> details.
> Hierdie boodskap en aanhangsels is aan 'n vrywaringsklousule onderhewig.
> Volledige besonderhede is by
> www.it.up.ac.za/documentation/governance/disclaimer/ beskikbaar.
> ===========================================
>
>

-- 
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan

  reply	other threads:[~2004-02-26  8:09 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-19 22:06 dm-crypt, new IV and standards Carl-Daniel Hailfinger
2004-02-19 22:20 ` Christophe Saout
2004-02-20 17:22   ` Jean-Luc Cooke
2004-02-20 21:26     ` James Morris
2004-02-20 21:52       ` 2.6.3 adaptec I2O will not compile David Lang
2004-02-25 16:25         ` Adrian Bunk
2004-02-26  8:02           ` Jaco Kroon
2004-02-26  8:08             ` David Lang [this message]
2004-02-26  9:28               ` Jaco Kroon
2004-02-26 10:24                 ` David Lang
2004-02-21  0:31       ` dm-crypt, new IV and standards Carl-Daniel Hailfinger
2004-02-21 16:48       ` Jean-Luc Cooke
2004-02-21 17:36         ` Jean-Luc Cooke
2004-02-21 19:01         ` Andreas Jellinghaus
2004-03-03  8:35         ` dean gaudet
2004-03-03 15:06           ` Jean-Luc Cooke
2004-03-03 21:40             ` David Wagner
2004-03-08 19:58               ` Jean-Luc Cooke
2004-03-04  1:48             ` dean gaudet
2004-03-04 13:24               ` Jean-Luc Cooke
2004-03-04 17:44                 ` David Wagner
2004-03-05  1:19                 ` dean gaudet
2004-03-05  2:14                   ` Jean-Luc Cooke
2004-03-04 15:08             ` Pavel Machek
2004-03-07  4:14               ` DM for detecting bad disks was: " Mike Fedyk
2004-02-26 14:56 2.6.3 adaptec I2O will not compile Salyzyn, Mark
2004-03-02  6:52 ` Jaco Kroon
     [not found] <547AF3BD0F3F0B4CBDC379BAC7E4189F38D76F@otce2k03.adaptec.com>
2004-03-16 14:20 ` Jaco Kroon

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=Pine.LNX.4.58.0402260007460.994@dlang.diginsite.com \
    --to=david.lang@digitalinsight.com \
    --cc=bunk@fs.tum.de \
    --cc=jkroon@cs.up.ac.za \
    --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

all inboxes | Powered by JetHome®