public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.8-pre4, lots of compile warnings
Date: Mon, 06 Aug 2001 19:52:31 +1000	[thread overview]
Message-ID: <3334.997091551@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Mon, 06 Aug 2001 11:49:10 +0200." <Pine.LNX.4.33.0108061138040.9237-100000@vaio>

On Mon, 6 Aug 2001 11:49:10 +0200 (CEST), 
Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de> wrote:
>On Mon, 6 Aug 2001, Keith Owens wrote:
>> 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
>
>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.

Add attribute unused plus a BIG comment saying that the code should be
moved to the new pci infrastructure ASAP.  Add the code to the janitor
list.


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

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-06  5:46 2.4.8-pre4, lots of compile warnings Keith Owens
2001-08-06  9:49 ` Kai Germaschewski
2001-08-06  9:52   ` Keith Owens [this message]
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=3334.997091551@ocs3.ocs-net \
    --to=kaos@ocs.com.au \
    --cc=kai@tp1.ruhr-uni-bochum.de \
    --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