[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20201112171826.0fa3c6158f3c2780f90faafe@linux-foundation.org>
Date: Thu, 12 Nov 2020 17:18:26 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Matteo Croce <mcroce@...ux.microsoft.com>
Cc: Nathan Chancellor <natechancellor@...il.com>,
Arnd Bergmann <arnd@...db.de>,
Kees Cook <keescook@...omium.org>,
linux-kernel@...r.kernel.org, Guenter Roeck <linux@...ck-us.net>,
Pavel Tatashin <pasha.tatashin@...een.com>,
Petr Mladek <pmladek@...e.com>,
Mike Rapoport <rppt@...nel.org>,
Tyler Hicks <tyhicks@...ux.microsoft.com>,
Nick Desaulniers <ndesaulniers@...gle.com>,
clang-built-linux@...glegroups.com
Subject: Re: [PATCH] reboot: Fix variable assignments in type_store
On Fri, 13 Nov 2020 01:20:29 +0100 Matteo Croce <mcroce@...ux.microsoft.com> wrote:
> While writing the script I found that in the documentation I left for
> 'type' the values from
> Documentation/admin-guide/kernel-parameters.txt, which is 'pci' for
> cf9_force reboot.
> While at it, should we update the doc with the values 'cf9_force' and
> 'cf9_safe', or rename to 'pci' and 'pci_safe' to be coherent with the
> kernel cmdline?
I looked at Documentation/admin-guide/kernel-parameters.txt's "reboot="
section and decided that I don't understand your above words :( Can you
please expand on all of this? Simple akpm-compatible words ;)
> In any case, kernel-parameters.txt doesn't mention that reboot=q does
> the 'cf9_safe' reboot type, so it must be fixed anyway.
Thanks for noticing.
Powered by blists - more mailing lists