From: Luis de Bethencourt <luisbg@osg.samsung.com>
To: linux-kernel@vger.kernel.org
Cc: akpm@linux-foundation.org, viro@zeniv.linux.org.uk,
salah.triki@gmail.com,
Luis de Bethencourt <luisbg@osg.samsung.com>
Subject: [PATCH 3/3] befs: fix typo in befs_bt_read_node documentation
Date: Tue, 12 Jul 2016 00:02:50 +0100 [thread overview]
Message-ID: <1468278170-3550-3-git-send-email-luisbg@osg.samsung.com> (raw)
In-Reply-To: <1468278170-3550-1-git-send-email-luisbg@osg.samsung.com>
Fixing a grammatical error in the documentation.
Signed-off-by: Luis de Bethencourt <luisbg@osg.samsung.com>
---
Hi,
Since befs_bt_read_node() calls befs_read_datastream(), and was touched
in the first commit of the series I decided to send a fix for the
grammatical error I had noticed there a while ago.
Thanks for all the reviews,
Luis
fs/befs/btree.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/fs/befs/btree.c b/fs/befs/btree.c
index 2b5b635..bf12b2c 100644
--- a/fs/befs/btree.c
+++ b/fs/befs/btree.c
@@ -181,8 +181,8 @@ befs_bt_read_super(struct super_block *sb, const befs_data_stream *ds,
* Calls befs_read_datastream to read in the indicated btree node and
* makes sure its header fields are in cpu byteorder, byteswapping if
* necessary.
- * Note: node->bh must be NULL when this function called first
- * time. Don't forget brelse(node->bh) after last call.
+ * Note: node->bh must be NULL when this function is called the first time.
+ * Don't forget brelse(node->bh) after last call.
*
* On success, returns BEFS_OK and *@node contains the btree node that
* starts at @node_off, with the node->head fields in cpu byte order.
--
2.5.3
next prev parent reply other threads:[~2016-07-11 23:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-11 23:02 [PATCH 1/3] befs: remove off argument of befs_read_datastream Luis de Bethencourt
2016-07-11 23:02 ` [PATCH 2/3] befs: in memory free_node_ptr and max_size never read Luis de Bethencourt
2016-07-11 23:02 ` Luis de Bethencourt [this message]
2016-07-27 23:37 ` [PATCH 1/3] befs: remove off argument of befs_read_datastream Salah Triki
2016-07-28 15:53 ` Luis de Bethencourt
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=1468278170-3550-3-git-send-email-luisbg@osg.samsung.com \
--to=luisbg@osg.samsung.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=salah.triki@gmail.com \
--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 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).