From: Michael Opdenacker <michael-lists@free-electrons.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Plans to obsolete register_chrdev()?
Date: Fri, 09 Jun 2006 17:00:57 +0200 [thread overview]
Message-ID: <44898D29.4030405@free-electrons.com> (raw)
Hello,
In Linux 2.6, character device driver developers are supposed to use
alloc_chrdev_region() and cdev_add() instead of register_chrdev(). See
http://lwn.net/images/pdf/LDD3/ch03.pdf or http://lwn.net/Articles/126808/ .
However, in 2.6.16, there are still *very few* uses of cdev_add().
Compare http://lxr.free-electrons.com/ident?i=cdev_add to
http://lxr.free-electrons.com/ident?i=register_chrdev .
Are there plans to officially obsolete register_chrdev() (in particular
through Documentation/feature-removal-schedule.txt)?
Unless register_chrdev() is supposed to stay, I'll be glad to
participate in converting character driver code. In particular, would
updateds to drivers/chars/mem.c file be welcome?
Cheers,
Michael.
--
Michael Opdenacker, Free Electrons
Free Embedded Linux Training Materials
on http://free-electrons.com/training
(More than 1000 pages!)
next reply other threads:[~2006-06-09 15:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-09 15:00 Michael Opdenacker [this message]
2006-06-12 8:14 ` Plans to obsolete register_chrdev()? Michael Opdenacker
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=44898D29.4030405@free-electrons.com \
--to=michael-lists@free-electrons.com \
--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