From: "Németh Márton" <nm127@freemail.hu>
To: Jens Axboe <axboe@kernel.dk>, Greg Kroah-Hartman <gregkh@suse.de>,
LKML <linux-kernel@vger.kernel.org>
Cc: Al Viro <viro@zeniv.linux.org.uk>, ltp-list@lists.sourceforge.net
Subject: [PATCH] block: add documentation for register_blkdev()
Date: Fri, 20 Feb 2009 07:04:52 +0100 [thread overview]
Message-ID: <499E4804.3030703@freemail.hu> (raw)
From: Márton Németh <nm127@freemail.hu>
Add documentation for register_blkdev() function and for the parameters.
Signed-off-by: Márton Németh <nm127@freemail.hu>
Cc: Greg Kroah-Hartman <gregkh@suse.de>
---
--- linux-2.6.29-rc5/block/genhd.c.orig 2009-02-14 18:36:39.000000000 +0100
+++ linux-2.6.29-rc5/block/genhd.c 2009-02-20 06:53:56.000000000 +0100
@@ -256,6 +256,22 @@ void blkdev_show(struct seq_file *seqf,
}
#endif /* CONFIG_PROC_FS */
+/**
+ * register_blkdev - register a new block device
+ *
+ * @major: the requested major device number [1..255]. If @major=0, try to
+ * allocate any unused major number.
+ * @name: the name of the new block device as a zero terminated string
+ *
+ * The @name must be unique within the system.
+ *
+ * The return value depends on the @major input parameter.
+ * - if a major device number was requested in range [1..255] then the
+ * function returns zero on success, or a negative error code
+ * - if any unused major number was requested with @major=0 parameter
+ * then the return value is the allocated major number in range
+ * [1..255] or a negative error code otherwise
+ */
int register_blkdev(unsigned int major, const char *name)
{
struct blk_major_name **n, *p;
next reply other threads:[~2009-02-20 6:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 6:04 Németh Márton [this message]
2009-02-20 7:12 ` [PATCH] block: add documentation for register_blkdev() Jens Axboe
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=499E4804.3030703@freemail.hu \
--to=nm127@freemail.hu \
--cc=axboe@kernel.dk \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ltp-list@lists.sourceforge.net \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.