Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.37 as permitted sender) client-ip=23.128.96.37;
Message-ID: <4257cc2a-c116-4a5a-8c4e-422e67258525@infradead.org>
Date:   Thu, 26 Oct 2023 21:41:06 -0700
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PATCH] docs: admin-guide: Update bootloader and installation
 instructions
Content-Language: en-US
To:     Hunter Chasens <hunter.chasens18@ncf.edu>, corbet@lwn.net
Cc:     linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
References: <20231027041023.16681-1-hunter.chasens18@ncf.edu>
From:   Randy Dunlap <rdunlap@infradead.org>
In-Reply-To: <20231027041023.16681-1-hunter.chasens18@ncf.edu>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: bulk


On 10/26/23 21:10, Hunter Chasens wrote:
> Updates the bootloader and installation instructions in admin-guide/README.rst
> to align with modern practices.
> 
> Details of Changes:
> 
>  - Added guidance on using EFISTUB for UEFI/EFI systems.
>  - Noted that LILO is no longer in active development and provides
>    alternatives.
>  - Kept LILO instructions but marked as Legacy LILO Instructions.
>    Suggest removal in future patch.
> 
> Signed-off-by: Hunter Chasens <hunter.chasens18@ncf.edu>
> ---
>  Documentation/admin-guide/README.rst | 71 ++++++++++++++++++----------
>  1 file changed, 46 insertions(+), 25 deletions(-)
> 
> diff --git a/Documentation/admin-guide/README.rst b/Documentation/admin-guide/README.rst
> index 9a969c0157f1..fba66f909f98 100644
> --- a/Documentation/admin-guide/README.rst
> +++ b/Documentation/admin-guide/README.rst
> @@ -252,7 +252,7 @@ Configuring the kernel
>      - The "kernel hacking" configuration details usually result in a
>        bigger or slower kernel (or both), and can even make the kernel
>        less stable by configuring some routines to actively try to
> -      break bad code to find kernel problems (kmalloc()).  Thus you

I don't see a problem with the above notation.

> +      break bad code to find kernel problems (kmalloc()().  Thus you

This way has unmatched parens.

>        should probably answer 'n' to the questions for "development",
>        "experimental", or "debugging" features.
>  


-- 
~Randy