From: Marcel Holtmann <marcel@holtmann.org>
To: Greg KH <greg@kroah.com>
Cc: Karsten Keil <kkeil@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux ISDN Mailing List <isdn4linux@listserv.isdn4linux.de>
Subject: Re: [PATCH] Add sysfs class support for CAPI
Date: Sat, 10 Apr 2004 22:16:27 +0200 [thread overview]
Message-ID: <1081628187.5398.36.camel@pegasus> (raw)
In-Reply-To: <20040409183220.GA16842@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 502 bytes --]
Hi Greg,
this patch fixes a bug in the CAPI TTY support, because the ->name value
of the TTY driver shouldn't contain a "/". After changing this there are
now a "capi20" TTY device and a "capi20" control device and so I renamed
the control device to "capi". The userspace visible part must be done by
udev and I added these two rules to restore the old namespace:
# CAPI devices
KERNEL="capi", NAME="capi20", SYMLINK="isdn/capi20"
KERNEL="capi*", NAME="capi/%n"
Regards
Marcel
[-- Attachment #2: patch --]
[-- Type: text/plain, Size: 722 bytes --]
===== drivers/isdn/capi/capi.c 1.52 vs edited =====
--- 1.52/drivers/isdn/capi/capi.c Sat Apr 10 22:04:37 2004
+++ edited/drivers/isdn/capi/capi.c Sat Apr 10 22:06:20 2004
@@ -1316,7 +1316,8 @@
drv->owner = THIS_MODULE;
drv->driver_name = "capi_nc";
- drv->name = "capi/";
+ drv->devfs_name = "capi/";
+ drv->name = "capi";
drv->major = capi_ttymajor;
drv->minor_start = 0;
drv->type = TTY_DRIVER_TYPE_SERIAL;
@@ -1492,7 +1493,7 @@
return PTR_ERR(capi_class);
}
- class_simple_device_add(capi_class, MKDEV(capi_major, 0), NULL, "capi20");
+ class_simple_device_add(capi_class, MKDEV(capi_major, 0), NULL, "capi");
devfs_mk_cdev(MKDEV(capi_major, 0), S_IFCHR | S_IRUSR | S_IWUSR,
"isdn/capi20");
next prev parent reply other threads:[~2004-04-10 20:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-09 13:22 Marcel Holtmann
2004-04-09 17:16 ` Greg KH
2004-04-09 18:13 ` Marcel Holtmann
2004-04-09 18:32 ` Greg KH
2004-04-10 20:16 ` Marcel Holtmann [this message]
2004-04-12 23:45 ` 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=1081628187.5398.36.camel@pegasus \
--to=marcel@holtmann.org \
--cc=greg@kroah.com \
--cc=isdn4linux@listserv.isdn4linux.de \
--cc=kkeil@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®