There are 2 typos (writeable,exlusively) in comments.
Fix it.
Signed-off-by: Zhang Jiaming <[email protected]>
---
block/bdev.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/block/bdev.c b/block/bdev.c
index 5fe06c1f2def..5c3754ed5689 100644
--- a/block/bdev.c
+++ b/block/bdev.c
@@ -272,7 +272,7 @@ EXPORT_SYMBOL(freeze_bdev);
* thaw_bdev -- unlock filesystem
* @bdev: blockdevice to unlock
*
- * Unlocks the filesystem and marks it writeable again after freeze_bdev().
+ * Unlocks the filesystem and marks it writable again after freeze_bdev().
*/
int thaw_bdev(struct block_device *bdev)
{
@@ -618,7 +618,7 @@ static void bd_clear_claiming(struct block_device *whole, void *holder)
* @bdev: block device of interest
* @holder: holder that has claimed @bdev
*
- * Finish exclusive open of a block device. Mark the device as exlusively
+ * Finish exclusive open of a block device. Mark the device as exclusively
* open by the holder and wake up all waiters for exclusive open to finish.
*/
static void bd_finish_claiming(struct block_device *bdev, void *holder)
@@ -830,7 +830,7 @@ struct block_device *blkdev_get_by_dev(dev_t dev, fmode_t mode, void *holder)
* Block event polling for write claims if requested. Any write
* holder makes the write_holder state stick until all are
* released. This is good enough and tracking individual
- * writeable reference is too fragile given the way @mode is
+ * writable reference is too fragile given the way @mode is
* used in blkdev_get/put().
*/
if ((mode & FMODE_WRITE) && !bdev->bd_write_holder &&
--
2.25.1