Commit 0117d427 authored by Mauro Carvalho Chehab's avatar Mauro Carvalho Chehab
Browse files

fs: add a blank lines on some kernel-doc comments 



Sphinx gets confused when it finds identation without a
good reason for it and without a preceding blank line:

	./fs/mpage.c:347: ERROR: Unexpected indentation.
	./fs/namei.c:4303: ERROR: Unexpected indentation.
	./fs/fs-writeback.c:2060: ERROR: Unexpected indentation.

No functional changes.

Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@s-opensource.com>
parent 76d0d5d3

fs/fs-writeback.c

+7 −5
Original line number Diff line number Diff line
@@ -2053,8 +2053,10 @@ static noinline void block_dump___mark_inode_dirty(struct inode *inode) 


/**

 * __mark_inode_dirty -	internal function

 *

 * @inode: inode to mark

 * @flags: what kind of dirty (i.e. I_DIRTY_SYNC)

 *

 * Mark an inode as dirty. Callers should use mark_inode_dirty or

 * mark_inode_dirty_sync.

 *

fs/mpage.c

+1 −0
Original line number Diff line number Diff line
@@ -344,6 +344,7 @@ confused: 
 *

 * So an mpage read of the first 16 blocks of an ext2 file will cause I/O to be

 * submitted in the following order:

 *

 * 	12 0 1 2 3 4 5 6 7 8 9 10 11 13 14 15 16

 *

 * because the indirect block has to be read to get the mappings of blocks

fs/namei.c

+1 −0
Original line number Diff line number Diff line
@@ -4300,6 +4300,7 @@ SYSCALL_DEFINE2(link, const char __user *, oldname, const char __user *, newname 
 * The worst of all namespace operations - renaming directory. "Perverted"

 * doesn't even start to describe it. Somebody in UCB had a heck of a trip...

 * Problems:

 *

 *	a) we can get into loop creation.

 *	b) race potential - two innocent renames can create a loop together.

 *	   That's where 4.4 screws up. Current fix: serialization on

CRA Git | Maintained and supported by SUSTech CRA and CCSE