All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: axboe@kernel.dk
Cc: linux-block@vger.kernel.org, Stephen Rothwell <sfr@canb.auug.org.au>
Subject: [PATCH 2/2] block: fixup the kerneldoc for lookup_bdev
Date: Tue, 22 Dec 2020 14:30:04 +0100	[thread overview]
Message-ID: <20201222133004.3016790-2-hch@lst.de> (raw)
In-Reply-To: <20201222133004.3016790-1-hch@lst.de>

Document the new dev parameter and the changed return value convention.

Signed-off-by: Christoph Hellwig <hch@lst.de>
Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
Fixes: 4e7b5671c6a8 ("block: remove i_bdev")
---
 fs/block_dev.c | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/fs/block_dev.c b/fs/block_dev.c
index 7633e5ac0885f7..d6ee0bb7005538 100644
--- a/fs/block_dev.c
+++ b/fs/block_dev.c
@@ -1828,10 +1828,11 @@ const struct file_operations def_blk_fops = {
 /**
  * lookup_bdev  - lookup a struct block_device by name
  * @pathname:	special file representing the block device
+ * @dev:	returns the dev_t for the device
  *
- * Get a reference to the blockdevice at @pathname in the current
- * namespace if possible and return it.  Return ERR_PTR(error)
- * otherwise.
+ * Find the dev_t for the block device at @pathname.  Returns 0 if there is a
+ * block device at @pathname, or a negative errno value if not.  The dev_t for
+ * the block device is placed in the variable pointed to by the @dev parameter.
  */
 int lookup_bdev(const char *pathname, dev_t *dev)
 {
-- 
2.29.2


      reply	other threads:[~2020-12-22 13:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-22 13:30 [PATCH 1/2] block: fixup the kerneldoc for bd_abort_claiming Christoph Hellwig
2020-12-22 13:30 ` Christoph Hellwig [this message]

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=20201222133004.3016790-2-hch@lst.de \
    --to=hch@lst.de \
    --cc=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.