[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4b710b02-b3a7-15ef-d1b9-c636352f41d1@igalia.com>
Date: Fri, 26 Nov 2021 18:34:16 -0300
From: "Guilherme G. Piccoli" <gpiccoli@...lia.com>
To: linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org
Cc: linux-doc@...r.kernel.org, mcgrof@...nel.org,
keescook@...omium.org, yzaikin@...gle.com,
akpm@...ux-foundation.org, feng.tang@...el.com,
siglesias@...lia.com, kernel@...ccoli.net
Subject: Re: [PATCH 0/3] Some improvements on panic_print
On 09/11/2021 17:28, Guilherme G. Piccoli wrote:
> Hey everybody, this is a mix of a documentation fix with some additions
> to the "panic_print" syscall / parameter. The goal here is being able
> to collect all CPUs backtraces during a panic event and also
> to enable "panic_print" in a kdump event - details of the reasoning
> and design choices in the patches.
>
> Thanks in advance for reviews!
> Cheers,
>
>
> Guilherme
>
Hi everybody, is there any feedback for this series?
Thanks in advance,
Guilherme
Powered by blists - more mailing lists