From: Greg KH <greg@kroah.com>
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.13 errors and warnings
Date: Sun, 28 Oct 2001 10:03:17 -0800 [thread overview]
Message-ID: <20011028100317.C8059@kroah.com> (raw)
In-Reply-To: <27909.1004263116@ocs3.intra.ocs.com.au>
In-Reply-To: <27909.1004263116@ocs3.intra.ocs.com.au>
On Sun, Oct 28, 2001 at 08:58:36PM +1100, Keith Owens wrote:
>
> drivers/usb/serial/belkin_sa.c:106: warning: `id_table_combined' defined but not used
> drivers/usb/serial/digi_acceleport.c:480: warning: `id_table_combined' defined but not used
> drivers/usb/serial/ftdi_sio.c:137: warning: `id_table_combined' defined but not used
> drivers/usb/serial/io_tables.h:33: warning: `id_table_combined' defined but not used
> drivers/usb/serial/keyspan.h:349: warning: `keyspan_ids_combined' defined but not used
> drivers/usb/serial/keyspan_pda.c:146: warning: `id_table_combined' defined but not used
> drivers/usb/serial/mct_u232.c:129: warning: `id_table_combined' defined but not used
> drivers/usb/serial/visor.c:171: warning: `id_table' defined but not used
> drivers/usb/serial/whiteheat.c:116: warning: `id_table_combined' defined but not used
These, and lots of the other pci_id table warnings are due to the tables
being used for MODULE_DEVICE_TABLE() information. When the code is not
compiled as modules, those tables are not needed.
Hm, I guess I should look into some kind of macro to keep this from
happening...
thanks,
greg k-h
next prev parent reply other threads:[~2001-10-28 18:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-28 9:58 2.4.13 errors and warnings Keith Owens
2001-10-28 18:03 ` Greg KH [this message]
2001-10-29 2:12 ` [patch] 2.4.13 remove unused warnings on module tables Keith Owens
2001-10-29 6:17 ` Jeff Garzik
2001-10-29 6:24 ` Keith Owens
2001-10-29 6:28 ` Jeff Garzik
2001-10-29 11:17 ` 2.4.13 errors and warnings Kai Germaschewski
2001-10-29 23:35 ` Greg KH
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=20011028100317.C8059@kroah.com \
--to=greg@kroah.com \
--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 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.