All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@clusterfs.com>
To: "James E. Hitzroth" <jhitzrot@digisle.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.7 compile errors w/ Compaq DL360 Smart2 controller
Date: Mon, 1 Apr 2002 14:17:13 -0700	[thread overview]
Message-ID: <20020401211713.GD3067@turbolinux.com> (raw)
In-Reply-To: <1017718659.1216.63.camel@jhitzcompaq>

On Apr 01, 2002  19:37 -0800, James E. Hitzroth wrote:
> File drivers/block/smart1,2.h
> 
> line 256  needs 'c' comment 
> 
>     242 static unsigned long smart1_completed(ctlr_info_t *h)
      :
      :
>     254 
>     255 
>     256 # error Please convert me to Documentation/DMA-mapping.txt

No, actually "#error" is a C pre-processor directive to cause the
compiler to generate an error at that spot (#warning generates a
compiler warning).

This was obviously put there by someone because this driver needs to be
updated to match a change in an API in the 2.5 kernel.  Making it a
comment means that either you will get a compile error anyways, but
without the useful pointer as to how it can be fixed, or worse - no
compile error but problems (including data corruption) later on.

I would do as the message states, and read DMA-mapping.txt to fix this.
Quite often kernel developers do not have access to all of the hardware
supported by Linux, so it is up to people like yourself who _do_ have
this hardware to fix it and test it - it is in your own best interest
to do so.

Cheers, Andreas
--
Andreas Dilger  \ "If a man ate a pound of pasta and a pound of antipasto,
                 \  would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/               -- Dogbert


      reply	other threads:[~2002-04-01 21:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-02  3:37 2.5.7 compile errors w/ Compaq DL360 Smart2 controller James E. Hitzroth
2002-04-01 21:17 ` Andreas Dilger [this message]

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=20020401211713.GD3067@turbolinux.com \
    --to=adilger@clusterfs.com \
    --cc=jhitzrot@digisle.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.