Btrfs: fix typos in comments (d4a78947) · Commits · e / devices / android_kernel_sony_msm8998

fs/btrfs/ctree.h

+11 −9

Original line number	Original line	Diff line number	Diff line
	@@ -143,12 +143,15 @@ static int btrfs_csum_sizes[] = { 4, 0 };
	#define BTRFS_FT_MAX 9		#define BTRFS_FT_MAX 9

	/*		/*
	* the key defines the order in the tree, and so it also defines (optimal)		* The key defines the order in the tree, and so it also defines (optimal)
	* block layout. objectid corresonds to the inode number. The flags		* block layout.
	* tells us things about the object, and is a kind of stream selector.		*
	* so for a given inode, keys with flags of 1 might refer to the inode		* objectid corresponds to the inode number.
	* data, flags of 2 may point to file data in the btree and flags == 3		*
	* may point to extents.		* type tells us things about the object, and is a kind of stream selector.
			* so for a given inode, keys with type of 1 might refer to the inode data,
			* type of 2 may point to file data in the btree and type == 3 may point to
			* extents.
	*		*
	* offset is the starting byte offset for this key in the stream.		* offset is the starting byte offset for this key in the stream.
	*		*
	@@ -200,7 +203,7 @@ struct btrfs_dev_item {

	/*		/*
	* starting byte of this partition on the device,		* starting byte of this partition on the device,
	* to allowr for stripe alignment in the future		* to allow for stripe alignment in the future
	*/		*/
	__le64 start_offset;		__le64 start_offset;

	@@ -958,7 +961,6 @@ struct btrfs_root {
	};		};

	/*		/*

	* inode items have the data typically returned from stat and store other		* inode items have the data typically returned from stat and store other
	* info about object characteristics. There is one for every file and dir in		* info about object characteristics. There is one for every file and dir in
	* the FS		* the FS
	@@ -989,7 +991,7 @@ struct btrfs_root {
	#define BTRFS_EXTENT_CSUM_KEY 128		#define BTRFS_EXTENT_CSUM_KEY 128

	/*		/*
	* root items point to tree roots. There are typically in the root		* root items point to tree roots. They are typically in the root
	* tree used by the super block to find all the other trees		* tree used by the super block to find all the other trees
	*/		*/
	#define BTRFS_ROOT_ITEM_KEY 132		#define BTRFS_ROOT_ITEM_KEY 132

fs/btrfs/locking.c

+2 −2

Original line number	Original line	Diff line number	Diff line
	@@ -60,8 +60,8 @@ void btrfs_clear_lock_blocking(struct extent_buffer *eb)

	/*		/*
	* unfortunately, many of the places that currently set a lock to blocking		* unfortunately, many of the places that currently set a lock to blocking
	* don't end up blocking for every long, and often they don't block		* don't end up blocking for very long, and often they don't block
	* at all. For a dbench 50 run, if we don't spin one the blocking bit		* at all. For a dbench 50 run, if we don't spin on the blocking bit
	* at all, the context switch rate can jump up to 400,000/sec or more.		* at all, the context switch rate can jump up to 400,000/sec or more.
	*		*
	* So, we're still stuck with this crummy spin on the blocking bit,		* So, we're still stuck with this crummy spin on the blocking bit,

fs/btrfs/volumes.h

+1 −1

Original line number	Original line	Diff line number	Diff line
	@@ -76,7 +76,7 @@ struct btrfs_device {
	struct btrfs_fs_devices {		struct btrfs_fs_devices {
	u8 fsid[BTRFS_FSID_SIZE]; /* FS specific uuid */		u8 fsid[BTRFS_FSID_SIZE]; /* FS specific uuid */

	/* the device with this id has the most recent coyp of the super */		/* the device with this id has the most recent copy of the super */
	u64 latest_devid;		u64 latest_devid;
	u64 latest_trans;		u64 latest_trans;
	u64 num_devices;		u64 num_devices;