From: Bean Huo <huobean@gmail.com>
To: axboe@kernel.dk, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: beanhuo@micron.com
Subject: [PATCH 1/2] block: use generic_file_buffered_read()
Date: Fri, 4 Sep 2020 11:13:40 +0200 [thread overview]
Message-ID: <20200904091341.28756-2-huobean@gmail.com> (raw)
In-Reply-To: <20200904091341.28756-1-huobean@gmail.com>
From: Bean Huo <beanhuo@micron.com>
do_generic_file_read() has been renamed to generic_file_buffered_read() since
commit 47c27bc46946 ("fs: pass iocb to do_generic_file_read").
Signed-off-by: Bean Huo <beanhuo@micron.com>
---
drivers/block/sunvdc.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/block/sunvdc.c b/drivers/block/sunvdc.c
index 39aeebc6837d..06262e990c9b 100644
--- a/drivers/block/sunvdc.c
+++ b/drivers/block/sunvdc.c
@@ -1017,9 +1017,9 @@ static int vdc_port_probe(struct vio_dev *vdev, const struct vio_device_id *id)
VDCBLK_NAME "%c", 'a' + ((int)vdev->dev_no % 26));
port->vdisk_size = -1;
- /* Actual wall time may be double due to do_generic_file_read() doing
- * a readahead I/O first, and once that fails it will try to read a
- * single page.
+ /* Actual wall time may be double due to generic_file_buffered_read()
+ * doing a readahead I/O first, and once that fails it will try to read
+ * a single page.
*/
ldc_timeout = mdesc_get_property(hp, vdev->mp, "vdc-timeout", NULL);
port->ldc_timeout = ldc_timeout ? *ldc_timeout : 0;
--
2.17.1
next prev parent reply other threads:[~2020-09-04 9:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-04 9:13 [PATCH 0/2] use generic_file_buffered_read() Bean Huo
2020-09-04 9:13 ` Bean Huo [this message]
2020-09-04 9:13 ` [PATCH 2/2] fs: isofs: " Bean Huo
2020-09-04 16:53 ` [PATCH 0/2] " Jens Axboe
2020-09-07 11:37 ` Bean Huo
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=20200904091341.28756-2-huobean@gmail.com \
--to=huobean@gmail.com \
--cc=axboe@kernel.dk \
--cc=beanhuo@micron.com \
--cc=linux-block@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).