mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andries.Brouwer@cwi.nl
To: Andries.Brouwer@cwi.nl, James.Bottomley@steeleye.com
Cc: James.Bottomley@SteelEye.com, linux-kernel@vger.kernel.org
Subject: Re: 3c509.c
Date: Wed, 22 Jan 2003 02:11:26 +0100 (MET)	[thread overview]
Message-ID: <UTC200301220111.h0M1BQg03940.aeb@smtp.cwi.nl> (raw)

    Please Don't do this:

    +#include <linux/mca-legacy.h>

    If you're getting MCA_NOTFOUND undefined, it's because
    CONFIG_MCA_LEGACY isn't set when mca.h is included
    (either because it's not in your kernel config, or 
    possibly because config.h isn't included into the right place
    in the driver---the latter doesn't look to be the problem
    for 3c509.c).

Yes, you are right. But.
(I do not have an MCA machine myself, this was just from
source inspection. Let me grep a bit more.)

Suppose CONFIG_MCA_LEGACY is not set, and CONFIG_MCA is set.
Then, as you say, <linux/mca-legacy.h> is not included.

Thus, the only definition of MCA_NOTFOUND is not seen.

Thus, all files that use it (eexpress.c, smctr.c, madgemc.c,
3c509.c, at1700.c, 3c523.c, depca.c, 3c527.c, sk_mca.c,
eicon_mod.c, ibmmca.c, mca_53c9x.c, fd_mcs.c, aha1542.c,
sim710.c, ps2esdi.c, sb_card.c) will not compile, if I am
not mistaken.

If you want to preserve the distinction between CONFIG_MCA and
CONFIG_MCA_LEGACY, then I suppose you want to replace the former
by the latter in all of the drivers mentioned?

Andries

             reply	other threads:[~2003-01-22  1:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-22  1:11 Andries.Brouwer [this message]
2003-01-22 16:44 ` 3c509.c James Bottomley
2003-01-22 16:57   ` 3c509.c Jeff Garzik
  -- strict thread matches above, loose matches on Subject: below --
2003-01-22 11:10 3c509.c Andries.Brouwer
2003-01-22 12:13 ` 3c509.c Marc Zyngier
2003-01-21 23:34 3c509.c James Bottomley
2003-01-21 20:45 3c509.c Andries.Brouwer
2003-01-22  9:29 ` 3c509.c Marc Zyngier

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=UTC200301220111.h0M1BQg03940.aeb@smtp.cwi.nl \
    --to=andries.brouwer@cwi.nl \
    --cc=James.Bottomley@steeleye.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

all inboxes | Powered by JetHome®