From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Rolf Eike Beer <eike-kernel@sf-tec.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] add function documentation for register_chrdev()
Date: Wed, 12 Jul 2006 08:53:19 -0700 [thread overview]
Message-ID: <20060712085319.0ae7b346.rdunlap@xenotime.net> (raw)
In-Reply-To: <200607120946.16501@bilbo.math.uni-mannheim.de>
On Wed, 12 Jul 2006 09:46:16 +0200 Rolf Eike Beer wrote:
> Documentation for register_chrdev() was missing completely.
I noticed that too.
Would you modify the patch to use the kernel-doc format, please?
See Documentation/kernel-doc-nano-HOWTO.txt or other source
files for examples.
and "-ve" is overused/overrated. :) Please use "negative".
(even though Andrew just used -ve yesterday)
> Signed-off-by: Rolf Eike Beer <eike-kernel@sf-tec.de>
>
> ---
> 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 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 a -ve errno 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)
> {
---
~Randy
next prev parent reply other threads:[~2006-07-12 15:50 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 [this message]
2006-07-13 6:49 ` Rolf Eike Beer
2006-07-13 7:09 ` [PATCH 1/2 v2] " Rolf Eike Beer
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=20060712085319.0ae7b346.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=eike-kernel@sf-tec.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®