public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Grzegorz Jaskiewicz <gj@pointblue.com.pl>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: linus <torvalds@transmeta.com>
Subject: [PATCH] 2.5.68-bk10 - usbkbd.c compilation error
Date: 30 Apr 2003 19:06:49 +0100	[thread overview]
Message-ID: <1051726009.21774.15.camel@gregs> (raw)

  gcc -Wp,-MD,drivers/usb/input/.usbkbd.o.d -D__KERNEL__ -Iinclude -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
-pipe -mpreferred-stack-boundary=2 -march=pentium4
-Iinclude/asm-i386/mach-default -fomit-frame-pointer -nostdinc
-iwithprefix include -DMODULE   -DKBUILD_BASENAME=usbkbd
-DKBUILD_MODNAME=usbkbd -c -o drivers/usb/input/.tmp_usbkbd.o
drivers/usb/input/usbkbd.c
drivers/usb/input/usbkbd.c:363: unknown field `devclass' specified in
initializer
drivers/usb/input/usbkbd.c:363: `input_devclass' undeclared here (not in
a function)
drivers/usb/input/usbkbd.c:363: initializer element is not constant
drivers/usb/input/usbkbd.c:363: (near initialization for
`usb_kbd_driver.driver.name')
drivers/usb/input/usbkbd.c:364: initializer element is not constant
drivers/usb/input/usbkbd.c:364: (near initialization for
`usb_kbd_driver.driver')
make[3]: *** [drivers/usb/input/usbkbd.o] Error 1
make[2]: *** [drivers/usb/input] Error 2
make[1]: *** [drivers/usb] Error 2
make: *** [drivers] Error 2

the same problem exists in usbmouse.c

changes are the same like in :
http://www.kernel.org/diff/diffview.cgi?file=%2Fpub%2Flinux%2Fkernel%2Fv2.5%2Fsnapshots%2Fincr%2Fpatch-2.5.68-bk9-bk10.bz2;z=74



This solves problem:

diff -u -r linux-2.5.68-bk10-org/drivers/usb/input/usbkbd.c
linux-2.5.68-bk10-changed/drivers/usb/input/usbkbd.c
--- linux-2.5.68-bk10-org/drivers/usb/input/usbkbd.c    2003-04-30
18:50:43.000000000 +0100
+++ linux-2.5.68-bk10-changed/drivers/usb/input/usbkbd.c       
2003-04-30 18:50:55.000000000 +0100
@@ -359,9 +359,6 @@
        .probe =        usb_kbd_probe,
        .disconnect =   usb_kbd_disconnect,
        .id_table =     usb_kbd_id_table,
-       .driver = {
-               .devclass = &input_devclass,
-       },
 };

 static int __init usb_kbd_init(void)
diff -u -r linux-2.5.68-bk10-org/drivers/usb/input/usbmouse.c
linux-2.5.68-bk10-changed/drivers/usb/input/usbmouse.c
--- linux-2.5.68-bk10-org/drivers/usb/input/usbmouse.c  2003-04-30
18:54:11.000000000 +0100
+++ linux-2.5.68-bk10-changed/drivers/usb/input/usbmouse.c     
2003-04-30 18:54:30.000000000 +0100
@@ -242,9 +242,6 @@
        .probe          = usb_mouse_probe,
        .disconnect     = usb_mouse_disconnect,
        .id_table       = usb_mouse_id_table,
-       .driver = {
-               .devclass = &input_devclass,
-       },
 };

 static int __init usb_mouse_init(void)

-- 
Grzegorz Jaskiewicz <gj@pointblue.com.pl>
K4 Labs


             reply	other threads:[~2003-04-30 17:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-30 18:06 Grzegorz Jaskiewicz [this message]
2003-04-30 18:34 ` [PATCH] 2.5.68-bk10 - usbkbd.c compilation error Greg KH
     [not found] <mailman.1051727220.20780.linux-kernel2news@redhat.com>
2003-04-30 22:12 ` Pete Zaitcev
2003-04-30 22:19   ` Randy.Dunlap
2003-04-30 22:26   ` Greg KH
2003-04-30 22:34     ` Grzegorz Jaskiewicz

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=1051726009.21774.15.camel@gregs \
    --to=gj@pointblue.com.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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