2
0
mirror of https://github.com/edk2-porting/linux-next.git synced 2024-12-24 13:13:57 +08:00
linux-next/drivers/isdn/capi
Stefan Schweizer 90d5ede598 [PATCH] Fix capi reload by unregistering the correct major
I am having the bug FATAL: Error inserting capi ([..]/capi.ko): Device or
resource busy when I try to reload capi after loading it.  in dmesg:
capi20: unable to get major 68

Fix the issue which is caused by setting the major to zero when registering
the chrdev succeeded.

(akpm: this means that we can again not use `major=0' (dynamic major
allocation) for this driver).

Cc: Karsten Keil <kkeil@suse.de>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-05-15 11:20:54 -07:00
..
capi.c [PATCH] Fix capi reload by unregistering the correct major 2006-05-15 11:20:54 -07:00
capidrv.c Linux-2.6.12-rc2 2005-04-16 15:20:36 -07:00
capidrv.h Linux-2.6.12-rc2 2005-04-16 15:20:36 -07:00
capifs.c [PATCH] mutex subsystem, semaphore to mutex: VFS, ->i_sem 2006-01-09 15:59:24 -08:00
capifs.h Linux-2.6.12-rc2 2005-04-16 15:20:36 -07:00
capilib.c Linux-2.6.12-rc2 2005-04-16 15:20:36 -07:00
capiutil.c Linux-2.6.12-rc2 2005-04-16 15:20:36 -07:00
kcapi_proc.c [PATCH] mark f_ops const in the inode 2006-03-28 09:16:05 -08:00
kcapi.c [PATCH] sem2mutex: kcapi.c 2006-03-23 07:38:10 -08:00
kcapi.h Linux-2.6.12-rc2 2005-04-16 15:20:36 -07:00
Kconfig Linux-2.6.12-rc2 2005-04-16 15:20:36 -07:00
Makefile Linux-2.6.12-rc2 2005-04-16 15:20:36 -07:00