From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: linux-kernel@vger.kernel.org
Cc: "Randy.Dunlap" <rdunlap@xenotime.net>
Subject: [PATCH 1/2 v2] add function documentation for register_chrdev()
Date: Thu, 13 Jul 2006 09:09:34 +0200 [thread overview]
Message-ID: <200607130909.34562@bilbo.math.uni-mannheim.de> (raw)
In-Reply-To: <200607120946.16501@bilbo.math.uni-mannheim.de>
Documentation for register_chrdev() was missing completely.
Signed-off-by: Rolf Eike Beer <eike-kernel@sf-tec.de>
---
commit 7471539cb5e9cdd7ca7e48a247e15797d0e53708
tree 6ecd75500615ae9a975835596afb820b0fa51786
parent e73ad26773b26c730c49f8ef3b00b10b8bcc0009
author Rolf Eike Beer <eike-kernel@sf-tec.de> Tue, 11 Jul 2006 15:29:09 +0200
committer Rolf Eike Beer <beer@siso-eb-i34d.silicon-software.de> Tue, 11 Jul 2006 15:29:09 +0200
fs/char_dev.c | 23 +++++++++++++++++++++++
1 files changed, 23 insertions(+), 0 deletions(-)
diff --git a/fs/char_dev.c b/fs/char_dev.c
index a4cbc67..ac28eaa 100644
--- a/fs/char_dev.c
+++ b/fs/char_dev.c
@@ -182,6 +182,29 @@ int alloc_chrdev_region(dev_t *dev, unsi
return 0;
}
+/*
+ * register_chrdev: register a major number for character devices.
+ *
+ * @major: major device number or 0 for dynamic allocation
+ * @name: name of this range of devices
+ * @fops: file operations associated with this devices
+ *
+ * If major == 0 this functions will dynamically allocate a major and return
+ * its number.
+ *
+ * If major > 0 this function will attempt to reserve a device with the given
+ * major number and will return zero on success.
+ *
+ * Returns negative error code on failure.
+ *
+ * The name of this device has nothing to do with the name of the device in
+ * /dev. It only helps to keep track of the different owners of devices. If
+ * your module name has only one type of devices it's ok to use e.g. the name
+ * of the module here.
+ *
+ * This function registers a range of 256 minor numbers. The first minor number
+ * is 0.
+ */
int register_chrdev(unsigned int major, const char *name,
const struct file_operations *fops)
{
next prev parent reply other threads:[~2006-07-13 7:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-12 7:42 [PATCH 0/2] Documentation improvements Rolf Eike Beer
2006-07-12 7:46 ` [PATCH 1/2] add function documentation for register_chrdev() Rolf Eike Beer
2006-07-12 15:53 ` Randy.Dunlap
2006-07-13 6:49 ` Rolf Eike Beer
2006-07-13 7:09 ` Rolf Eike Beer [this message]
2006-07-12 7:47 ` [PATCH 2/2] Remove pci_dac_set_dma_mask() from Documentation/DMA-mapping.txt Rolf Eike Beer
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=200607130909.34562@bilbo.math.uni-mannheim.de \
--to=eike-kernel@sf-tec.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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