Subject: Re: [PATCH 0/3] Some improvements on panic_print
To:     linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Cc:     linux-doc@vger.kernel.org, mcgrof@kernel.org,
        keescook@chromium.org, yzaikin@google.com,
        akpm@linux-foundation.org, feng.tang@intel.com,
        siglesias@igalia.com, kernel@gpiccoli.net
References: <20211109202848.610874-1-gpiccoli@igalia.com>
From:   "Guilherme G. Piccoli" <gpiccoli@igalia.com>
Message-ID: <4b710b02-b3a7-15ef-d1b9-c636352f41d1@igalia.com>
Date:   Fri, 26 Nov 2021 18:34:16 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.13.0
MIME-Version: 1.0
In-Reply-To: <20211109202848.610874-1-gpiccoli@igalia.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk

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