All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Brosius <cobra@compuserve.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [2.5.43] (DAC960 compile failure)
Date: Wed, 16 Oct 2002 19:28:07 -0400	[thread overview]
Message-ID: <3DADF607.4B83C107@compuserve.com> (raw)

> 
>  looking at that i realise that DAC960 code in 2.5.43
> is not supposed to be tested:
> ======
> #error I am a non-portable driver, please convert me to use the Documentation/DMA-mapping.txt interfaces
> ======
>  am i right?
> 
> the following weirdo appears in both gcc-3.1 and 3.2 (also in 2.5.42)
> ======
> drivers/block/DAC960.c: In function `DAC960_DetectControllers':
> drivers/block/DAC960.c:2465: `Controller' undeclared (first use in this function)
> drivers/block/DAC960.c:2465: (Each undeclared identifier is reported only once
> drivers/block/DAC960.c:2465: for each function it appears in.)
> 

Yes, 2.5.42 did this also.  It looks like gcc 3.2 doesn't like goto's
which reference variables outside their native scope.  You can move the
Controller definition to full function scope to fix that error.

The DAC960 doesn't seem usable out of the stock kernel build though. 
You'll need to try patches previously posted to the list.  (Which don't
fully work for me either...)

-- 
Kevin

             reply	other threads:[~2002-10-16 23:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-16 23:28 Kevin Brosius [this message]
2002-10-17  0:36 ` [2.5.43] (DAC960 compile failure) Dave Olien
  -- strict thread matches above, loose matches on Subject: below --
2002-10-17 15:49 Kevin Brosius

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=3DADF607.4B83C107@compuserve.com \
    --to=cobra@compuserve.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 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.