From: Zhang Jiaming <jiaming@nfschina.com>
To: dushistov@mail.ru
Cc: linux-kernel@vger.kernel.org, liqiong@nfschina.com,
renyu@nfschina.com, Zhang Jiaming <jiaming@nfschina.com>
Subject: [PATCH] fs: Add space after ',' and Fix typo
Date: Wed, 29 Jun 2022 20:16:06 +0800 [thread overview]
Message-ID: <20220629121606.9727-1-jiaming@nfschina.com> (raw)
Add blank space after ','.
Change 'maped' to 'mapped'.
Signed-off-by: Zhang Jiaming <jiaming@nfschina.com>
---
fs/ufs/inode.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/fs/ufs/inode.c b/fs/ufs/inode.c
index a873de7dec1c..3265ab820815 100644
--- a/fs/ufs/inode.c
+++ b/fs/ufs/inode.c
@@ -54,7 +54,7 @@ static int ufs_block_to_path(struct inode *inode, sector_t i_block, unsigned off
int n = 0;
- UFSD("ptrs=uspi->s_apb = %d,double_blocks=%ld \n",ptrs,double_blocks);
+ UFSD("ptrs=uspi->s_apb = %d, double_blocks=%ld \n", ptrs, double_blocks);
if (i_block < direct_blocks) {
offsets[n++] = i_block;
} else if ((i_block -= direct_blocks) < indirect_blocks) {
@@ -469,7 +469,7 @@ static int ufs_getfrag_block(struct inode *inode, sector_t fragment, struct buff
static int ufs_writepage(struct page *page, struct writeback_control *wbc)
{
- return block_write_full_page(page,ufs_getfrag_block,wbc);
+ return block_write_full_page(page, ufs_getfrag_block, wbc);
}
static int ufs_read_folio(struct file *file, struct folio *folio)
@@ -521,7 +521,7 @@ static int ufs_write_end(struct file *file, struct address_space *mapping,
static sector_t ufs_bmap(struct address_space *mapping, sector_t block)
{
- return generic_block_bmap(mapping,block,ufs_getfrag_block);
+ return generic_block_bmap(mapping, block, ufs_getfrag_block);
}
const struct address_space_operations ufs_aops = {
@@ -1088,7 +1088,7 @@ static int ufs_alloc_lastblock(struct inode *inode, loff_t size)
clean_bdev_bh_alias(bh);
/*
* we do not zeroize fragment, because of
- * if it maped to hole, it already contains zeroes
+ * if it mapped to hole, it already contains zeroes
*/
set_buffer_uptodate(bh);
mark_buffer_dirty(bh);
--
2.25.1
reply other threads:[~2022-06-29 12:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220629121606.9727-1-jiaming@nfschina.com \
--to=jiaming@nfschina.com \
--cc=dushistov@mail.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=liqiong@nfschina.com \
--cc=renyu@nfschina.com \
/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