From: Jackie Liu <liu.yun@linux.dev>
To: axboe@kernel.dk, hch@lst.de
Cc: linux-fsdevel@vger.kernel.org, linux-block@vger.kernel.org,
liu.yun@linux.dev
Subject: [PATCH 1/2] fs: bdev: fix conflicting comment from lookup_bdev
Date: Thu, 21 Oct 2021 15:13:43 +0800 [thread overview]
Message-ID: <20211021071344.1600362-1-liu.yun@linux.dev> (raw)
From: Jackie Liu <liuyun01@kylinos.cn>
We switched to directly use dev_t to get block device, lookup changed the
meaning of use, now we fix this conflicting comment.
Fixes: 4e7b5671c6a8 ("block: remove i_bdev")
Cc: Jens Axboe <axboe@kernel.dk>
Cc: Christoph Hellwig <hch@lst.de>
Cc: linux-fsdevel@vger.kernel.org
Signed-off-by: Jackie Liu <liuyun01@kylinos.cn>
---
block/bdev.c | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/block/bdev.c b/block/bdev.c
index 485a258b0ab3..51d69243d315 100644
--- a/block/bdev.c
+++ b/block/bdev.c
@@ -962,9 +962,11 @@ EXPORT_SYMBOL(blkdev_put);
* @pathname: special file representing the block device
* @dev: return value of the block device's dev_t
*
- * Get a reference to the blockdevice at @pathname in the current
- * namespace if possible and return it. Return ERR_PTR(error)
- * otherwise.
+ * Lookup the block device's dev_t at @pathname in the current
+ * namespace if possible and return it by @dev.
+ *
+ * RETURNS:
+ * 0 if succeeded, errno otherwise.
*/
int lookup_bdev(const char *pathname, dev_t *dev)
{
--
2.25.1
next reply other threads:[~2021-10-21 7:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-21 7:13 Jackie Liu [this message]
2021-10-21 7:13 ` [PATCH 2/2] scsi: bsg: fix errno when scsi_bsg_register_queue fails Jackie Liu
2021-10-21 7:33 ` Christoph Hellwig
2021-10-21 7:32 ` [PATCH 1/2] fs: bdev: fix conflicting comment from lookup_bdev Christoph Hellwig
2021-10-21 14:24 ` Jens Axboe
2021-10-21 14:35 ` 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=20211021071344.1600362-1-liu.yun@linux.dev \
--to=liu.yun@linux.dev \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).