The patch titled
Fix capi reload by unregistering the correct major
has been removed from the -mm tree. Its filename is
fix-capi-reload-by-unregistering-the-correct-major.patch
This patch was probably dropped from -mm because
it has now been merged into a subsystem tree or
into Linus's tree, or because it was folded into
its parent patch in the -mm tree.
From: Stefan Schweizer <genstef@xxxxxxxxxx>
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@xxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxx>
---
drivers/isdn/capi/capi.c | 1 -
1 files changed, 1 deletion(-)
diff -puN drivers/isdn/capi/capi.c~fix-capi-reload-by-unregistering-the-correct-major drivers/isdn/capi/capi.c
--- devel/drivers/isdn/capi/capi.c~fix-capi-reload-by-unregistering-the-correct-major 2006-05-15 09:43:24.000000000 -0700
+++ devel-akpm/drivers/isdn/capi/capi.c 2006-05-15 09:43:24.000000000 -0700
@@ -1499,7 +1499,6 @@ static int __init capi_init(void)
printk(KERN_ERR "capi20: unable to get major %d\n", capi_major);
return major_ret;
}
- capi_major = major_ret;
capi_class = class_create(THIS_MODULE, "capi");
if (IS_ERR(capi_class)) {
unregister_chrdev(capi_major, "capi20");
_
Patches currently in -mm which might be from genstef@xxxxxxxxxx are
origin.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
