public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dale Amon <amon@vnl.com>
To: Frank Davis <fdavis@si.rr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.5.24 : BusLogic cleanup
Date: Thu, 18 Jul 2002 12:18:47 +0100	[thread overview]
Message-ID: <20020718111847.GF19403@vnl.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0206240104380.922-100000@localhost.localdomain>

On Mon, Jun 24, 2002 at 01:07:18AM -0400, Frank Davis wrote:
> Hello all,
>   The following patch removes some unneccessary (it seems) typedefs, and 
> adds in the pci_set_dma_mask() check mentioned in 
> Documentation/DMA-mapping.txt . Please review.

Did your Buslogic patch ever get included? I'm still
getting errors compiling 2.5.x as of .26 last night:

BusLogic.c:32: #error Please convert me to Documentation/DMA-mapping.txt
BusLogic.c: In function `BusLogic_DetectHostAdapter':
BusLogic.c:2841: warning: long unsigned int format, BusLogic_IO_Address_T arg (arg 2)
BusLogic.c: In function `BusLogic_QueueCommand':
BusLogic.c:3415: structure has no member named `address'
BusLogic.c: In function `BusLogic_BIOSDiskParameters':
BusLogic.c:4141: warning: implicit declaration of function `scsi_bios_ptable'
BusLogic.c:4141: warning: assignment makes pointer from integer without a cast
make[2]: *** [BusLogic.o] Error 1

Given that your patch was against .24, I would guess
it should be "relatively" safe against a .26 since it's
only driver code that everyone else seems to be ignoring.

  reply	other threads:[~2002-07-18 11:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-24  5:07 [PATCH] 2.5.24 : BusLogic cleanup Frank Davis
2002-07-18 11:18 ` Dale Amon [this message]
2002-07-18 13:02   ` Zwane Mwaikambo
     [not found]     ` <3D36CC41.8070409@si.rr.com>
     [not found]       ` <20020718142829.GC4358@vnl.com>
     [not found]         ` <3D36D8F1.2040803@si.rr.com>
2002-07-18 15:15           ` [PATCH] 2.5.24 : BusLogic cleanup - architecture dependencies Dale Amon

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=20020718111847.GF19403@vnl.com \
    --to=amon@vnl.com \
    --cc=fdavis@si.rr.com \
    --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