fs/cramfs/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Fix spelling and hyphenation in cramfs Kconfig.
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Nicolas Pitre <nico@fluxnic.net>
---
fs/cramfs/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -- a/fs/cramfs/Kconfig b/fs/cramfs/Kconfig
--- 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.
On Tue, 24 Jan 2023, Randy Dunlap wrote: > Fix spelling and hyphenation in cramfs Kconfig. > > Signed-off-by: Randy Dunlap <rdunlap@infradead.org> > Cc: Nicolas Pitre <nico@fluxnic.net> Acked-by: Nicolas Pitre <nico@fluxnic.net> cramfs is very low volume in terms of changes so please take this along with other trivias directly. > --- > fs/cramfs/Kconfig | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff -- a/fs/cramfs/Kconfig b/fs/cramfs/Kconfig > --- 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. >
© 2016 - 2025 Red Hat, Inc.