From: Luis Chamberlain <mcgrof@kernel.org>
To: "Guilherme G. Piccoli" <gpiccoli@igalia.com>
Cc: Feng Tang <feng.tang@intel.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-doc@vger.kernel.org, keescook@chromium.org,
yzaikin@google.com, akpm@linux-foundation.org,
siglesias@igalia.com, kernel@gpiccoli.net
Subject: Re: [PATCH 2/3] panic: Add option to dump all CPUs backtraces in panic_print
Date: Sun, 19 Dec 2021 12:11:40 -0800 [thread overview]
Message-ID: <Yb+R/OVeBkdYLWeH@bombadil.infradead.org> (raw)
In-Reply-To: <6f269857-2cbe-b4dd-714a-82372dc3adfc@igalia.com>
On Fri, Dec 03, 2021 at 12:09:06PM -0300, Guilherme G. Piccoli wrote:
> On 30/11/2021 02:12, Feng Tang wrote:
> > On Tue, Nov 09, 2021 at 05:28:47PM -0300, Guilherme G. Piccoli wrote:
> >> [...]
> > This looks to be helpful for debugging panic.
> >
> > Reviewed-by: Feng Tang <feng.tang@intel.com>
> >
> > Thanks,
> > Feng
>
> Thanks a lot Feng, for both your reviews! Do you have any opinions about
> patch 3?
>
> Also, as a generic question to all CCed, what is the way forward with
> this thread?
> Cheers,
mcgrof@sumo ~/linux-next (git::master)$ ./scripts/get_maintainer.pl
kernel/printk/
Petr Mladek <pmladek@suse.com> (maintainer:PRINTK)
Sergey Senozhatsky <senozhatsky@chromium.org> (maintainer:PRINTK)
Steven Rostedt <rostedt@goodmis.org> (reviewer:PRINTK)
John Ogness <john.ogness@linutronix.de> (reviewer:PRINTK)
linux-kernel@vger.kernel.org (open list)
So I suggest you email the patches to those.
Luis
next prev parent reply other threads:[~2021-12-19 20:11 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-09 20:28 [PATCH 0/3] Some improvements on panic_print Guilherme G. Piccoli
2021-11-09 20:28 ` [PATCH 1/3] docs: sysctl/kernel: Add missing bit to panic_print Guilherme G. Piccoli
2021-11-30 5:09 ` Feng Tang
2021-11-09 20:28 ` [PATCH 2/3] panic: Add option to dump all CPUs backtraces in panic_print Guilherme G. Piccoli
2021-11-30 5:12 ` Feng Tang
2021-12-03 15:09 ` Guilherme G. Piccoli
2021-12-19 20:11 ` Luis Chamberlain [this message]
2021-12-20 12:38 ` Guilherme G. Piccoli
2021-12-21 23:48 ` Andrew Morton
2021-12-22 12:37 ` Guilherme G. Piccoli
2022-01-13 9:31 ` Petr Mladek
2021-11-09 20:28 ` [PATCH 3/3] panic: Allow printing extra panic information on kdump Guilherme G. Piccoli
2021-12-22 11:45 ` Dave Young
2021-12-22 12:34 ` Guilherme G. Piccoli
2021-12-24 1:35 ` Dave Young
2021-12-25 19:21 ` Guilherme G. Piccoli
2021-12-27 1:45 ` Dave Young
2021-12-27 3:14 ` Guilherme G. Piccoli
2022-01-13 9:02 ` Petr Mladek
2022-01-13 13:00 ` Guilherme G. Piccoli
2022-01-27 16:53 ` Guilherme G. Piccoli
2022-02-08 18:12 ` Guilherme G. Piccoli
2022-02-08 21:39 ` Stephen Rothwell
2022-02-09 15:06 ` Guilherme G. Piccoli
2022-02-09 23:26 ` Stephen Rothwell
2022-02-10 12:50 ` Guilherme G. Piccoli
2021-11-26 21:34 ` [PATCH 0/3] Some improvements on panic_print Guilherme G. Piccoli
2021-12-14 16:31 ` Guilherme G. Piccoli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Yb+R/OVeBkdYLWeH@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=feng.tang@intel.com \
--cc=gpiccoli@igalia.com \
--cc=keescook@chromium.org \
--cc=kernel@gpiccoli.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=siglesias@igalia.com \
--cc=yzaikin@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).