Commit e0439977 authored Jan 03, 2025 by Li Zhijian Committed by Jonathan Corbet Jan 09, 2025

Documentation: Fix typo localmodonfig -> localmodconfig



It's noticed when I myself made the same spelling mistake while
searching for localmodconfig

Signed-off-by: Li Zhijian <lizhijian@fujitsu.com>
Reviewed-by: Thorsten Leemhuis <linux@leemhuis.info>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Link: https://lore.kernel.org/r/20250103004358.1310121-1-lizhijian@fujitsu.com

parent a8837641

Documentation/admin-guide/quickly-build-trimmed-linux.rst

+1 −1

Original line number	Diff line number	Diff line
		@@ -733,7 +733,7 @@ can easily happen that your self-built kernel will lack modules for tasks you
		did not perform before utilizing this make target. That's because those tasks
		require kernel modules that are normally autoloaded when you perform that task
		for the first time; if you didn't perform that task at least once before using
		localmodonfig, the latter will thus assume these modules are superfluous and
		localmodconfig, the latter will thus assume these modules are superfluous and
		disable them.

		You can try to avoid this by performing typical tasks that often will autoload

Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst

+1 −1

Original line number	Diff line number	Diff line
		@@ -1431,7 +1431,7 @@ can easily happen that your self-built kernels will lack modules for tasks you
		did not perform at least once before utilizing this make target. That happens
		when a task requires kernel modules which are only autoloaded when you execute
		it for the first time. So when you never performed that task since starting your
		kernel the modules will not have been loaded -- and from localmodonfig's point
		kernel the modules will not have been loaded -- and from localmodconfig's point
		of view look superfluous, which thus disables them to reduce the amount of code
		to be compiled.