mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
To: Keith Owens <kaos@ocs.com.au>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.8-pre4, lots of compile warnings
Date: Mon, 6 Aug 2001 11:49:10 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.33.0108061138040.9237-100000@vaio> (raw)
In-Reply-To: <848.997076771@ocs3.ocs-net>

On Mon, 6 Aug 2001, Keith Owens wrote:

> As part of stress testing kbuild 2.5, I built a 2.4.8-pre4 ix86 kernel
> with almost every option turned on, the .config is at the end.  It got
> a lot of warnings, I hope that the maintainers will do something about
> these.  Do not send patches to me, send them to the list or the
> maintainer.

> drivers/isdn/hisax/config.c:1720: warning: `hisax_pci_tbl' defined but not used
> drivers/isdn/avmb1/b1pci.c:31: warning: `b1pci_pci_tbl' defined but not used
> drivers/isdn/avmb1/t1pci.c:34: warning: `t1pci_pci_tbl' defined but not used
> drivers/isdn/avmb1/c4.c:39: warning: `c4_pci_tbl' defined but not used

[lots of similar warnings in non-ISDN code skipped]

This warning is seen a lot when compiling drivers into the kernel which 
have not been adapted to the new pci infrastructure yet.

This drivers contain the device table only for informational purposes, 
i.e. it's not referenced in a struct pci_driver, but only as 
MODULE_DEVICE_TABLE.

When compiling built-in, MODULE_DEVICE_TABLE is a no-op and thus the
device table is not referenced.

I can think of multiple ways to fix this:

o Move drivers to the new pci infrastructure. This is of course the
  best solution in the long run, but in many cases not appropriate for 
  2.4.
o Add an __attribute__((unused)) to the definition of the table. Ugly.
o Add an #ifdef MODULE around the definition of the table. Ugly.
o Make MODULE_DEVICE_TABLE reference the table also in the built-in case.
  Wastes space, as it really is never used, but not a lot of it.
o Live with the warnings.
o [fill in you suggestion]

If we can agree on how to handle this in a generic way, I can surely come 
up with a patch.

--Kai


  reply	other threads:[~2001-08-06  9:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-06  5:46 Keith Owens
2001-08-06  9:49 ` Kai Germaschewski [this message]
2001-08-06  9:52   ` Keith Owens
2001-08-06 10:54     ` Kai Germaschewski
2001-08-06 12:13       ` Christoph Hellwig
2001-08-06 12:50         ` Kai Germaschewski
2001-08-06 22:25 ` Matthew Gardiner

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.33.0108061138040.9237-100000@vaio \
    --to=kai@tp1.ruhr-uni-bochum.de \
    --cc=kaos@ocs.com.au \
    --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®