Hi!

> +If your platform uses techniques like Secure Boot, prepare the system to permit
> +starting self-compiled Linux kernels; install compilers and everything else
> +needed for building Linux; make sure to have 15 Gigabyte free space in your home
> +directory. Now run the following commands to download the sources of Linux,
> +which you then use to configure, build and install your own
> kernel::

15GB is quite a lot. Maybe the shallow clone should be given another
chance?

> +       mkdir ~/linux/ ~/linux/sources ~/linux/build
> +       git clone https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git \
> +         ~/linux/sources
> +       cd ~/linux/sources/
> +       # hint: if you don't want to build any stable or longterm kernels, skip the
> +       #   next two commands
> +       git remote add linux-stable \
> +         https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
> +       git fetch --all
> +       # hint: if you want to apply patches, do it at this point (see below for details)
> +       # hint: at this point it's recommended to tag your build (see below for details)
> +       yes "" | make O=~/linux/build/ localmodconfig
> +       # hint: at this point you might want or have to adjust the build configuration
> +       #  (see below for details)
> +       # note: if you are running a Debian kernel, you'll have to adjust the configuration
> +       #  at this point (see below)
> +       make -j $(nproc --all) O=~/linux/build/

Is the complexity of using O= worth it for one-off kernel builds?

Best regards,
								Pavel
-- 
People of Russia, stop Putin before his war on Ukraine escalates.