From: "Stephen Biggs" <yrgrknmxpzlk@gawab.com>
To: kernel-janitors@vger.kernel.org
Subject: [KJ] [PATCH][17/26] drivers/usb/class/* - compile warning cleanup
Date: Thu, 10 Feb 2005 21:34:28 +0000 [thread overview]
Message-ID: <420BEF84.30631.5873DC@localhost> (raw)
[-- Attachment #1: Mail message body --]
[-- Type: text/plain, Size: 998 bytes --]
Description: add MODULE definition compile fence so MODULE_DEVICE_TABLE
vars not declared when compiled into the kernel
Signed-off-by: Stephen Biggs <yrgrknmxpzlk@gawab.com>
diff -Nurdp -X dontdiff-osdl linux-2.6.11-rc3-mm-original/drivers/usb/class/usb-midi.h linux-2.6.11-rc3-mm/drivers/usb/class/usb-midi.h
--- linux-2.6.11-rc3-mm-original/drivers/usb/class/usb-midi.h 2005-02-03 03:56:10.000000000 +0200
+++ linux-2.6.11-rc3-mm/drivers/usb/class/usb-midi.h 2005-02-07 21:19:25.000000000 +0200
@@ -139,6 +139,7 @@ static struct usb_midi_device usb_midi_d
#define VENDOR_SPECIFIC_USB_MIDI_DEVICES (sizeof(usb_midi_devices)/sizeof(struct usb_midi_device))
+#ifdef MODULE
/* for Hot-Plugging */
static struct usb_device_id usb_midi_ids [] = {
@@ -157,6 +158,7 @@ static struct usb_device_id usb_midi_ids
};
MODULE_DEVICE_TABLE (usb, usb_midi_ids);
+#endif /* MODULE */
/* ------------------------------------------------------------------------- */
#endif /* _USB_MIDI_H_ */
[-- Attachment #2: Type: text/plain, Size: 167 bytes --]
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors
next reply other threads:[~2005-02-10 21:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-10 21:34 Stephen Biggs [this message]
2005-02-10 22:15 ` [KJ] [PATCH][17/26] drivers/usb/class/* - compile warning cleanup Greg KH
2005-02-11 0:32 ` Stephen Biggs
2005-02-11 0:47 ` 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=420BEF84.30631.5873DC@localhost \
--to=yrgrknmxpzlk@gawab.com \
--cc=kernel-janitors@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.