From: Colin Ian King <[email protected]>
There is a spelling mistake in the Kconfig text. Fix it.
Signed-off-by: Colin Ian King <[email protected]>
---
fs/cramfs/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/cramfs/Kconfig b/fs/cramfs/Kconfig
index d98cef0dbb6b..a8af8c6ac15d 100644
--- a/fs/cramfs/Kconfig
+++ b/fs/cramfs/Kconfig
@@ -38,7 +38,7 @@ config CRAMFS_MTD
default y if !CRAMFS_BLOCKDEV
help
This option allows the CramFs driver to load data directly from
- a linear adressed memory range (usually non volatile memory
+ a linear addressed memory range (usually non volatile memory
like flash) instead of going through the block device layer.
This saves some memory since no intermediate buffering is
necessary.
--
2.31.1
On Sun, 4 Jul 2021, Colin King wrote:
> From: Colin Ian King <[email protected]>
>
> There is a spelling mistake in the Kconfig text. Fix it.
>
> Signed-off-by: Colin Ian King <[email protected]>
Acked-by: Nicolas Pitre <[email protected]>
> ---
> fs/cramfs/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/cramfs/Kconfig b/fs/cramfs/Kconfig
> index d98cef0dbb6b..a8af8c6ac15d 100644
> --- a/fs/cramfs/Kconfig
> +++ b/fs/cramfs/Kconfig
> @@ -38,7 +38,7 @@ config CRAMFS_MTD
> default y if !CRAMFS_BLOCKDEV
> help
> This option allows the CramFs driver to load data directly from
> - a linear adressed memory range (usually non volatile memory
> + a linear addressed memory range (usually non volatile memory
> like flash) instead of going through the block device layer.
> This saves some memory since no intermediate buffering is
> necessary.
> --
> 2.31.1
>
>