From: Greg KH <gregkh@linuxfoundation.org>
To: Hongyu Xie <xiehongyu1@kylinos.cn>
Cc: linux@armlinux.org.uk, jirislaby@kernel.org, corbet@lwn.net,
rdunlap@infradead.org, linux-serial@vger.kernel.org,
linux-kernel@vger.kernel.org, xy521521@gmail.com,
oe-kbuild-all@lists.linux.dev, lkp@intel.com,
bagasdotme@gmail.com
Subject: Re: [RESEND PATCH v4 -next] tty: serial: add panic serial helper
Date: Fri, 16 Jun 2023 08:03:35 +0200 [thread overview]
Message-ID: <2023061606-hunk-overdraft-8d04@gregkh> (raw)
In-Reply-To: <fbfbbad5-2418-5c1a-87f1-dc2ca20204aa@kylinos.cn>
On Fri, Jun 16, 2023 at 10:31:15AM +0800, Hongyu Xie wrote:
> 在 2023/6/15 18:17, Greg KH 写道:
> > On Wed, Jun 14, 2023 at 10:55:12AM +0800, Hongyu Xie wrote:
> > > It was inspired by kgdboc.
> > >
> > > This is a debug module that allows you to get all kernel logs
> > > after panic.
> > >
> > > Normally you need to attach a USB-to-UART tool or enable kdump
> > > before panic happens to get log from kernel after panic. If you
> > > didn't do that and kdump is not working, you can't get any log to
> > > know what happened before panic. If you have a USB-to-UART tool
> > > and the UART port on your computer is working. This module helps
> > > you to get all kernel log after panic() is called.
> > >
> > > To use this, see Documentation/dev-tools/panic_serial_helper.rst.
> > >
> > > Tested on an arm64 device.
> > >
> > > Signed-off-by: Hongyu Xie <xiehongyu1@kylinos.cn>
> > > ---
> >
> > Why is this a RESEND? What's wrong with the previous version?
> Nobody review v4 for over a week.
That's fine, but you need to say _why_ this is being resent, otherwise
we have no idea, and this just moves to the bottom of our review queue.
thanks,
greg k-h
next prev parent reply other threads:[~2023-06-16 6:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 2:55 [RESEND PATCH v4 -next] tty: serial: add panic serial helper Hongyu Xie
2023-06-15 10:17 ` Greg KH
2023-06-16 2:31 ` Hongyu Xie
2023-06-16 6:03 ` Greg KH [this message]
2023-06-16 6:19 ` Hongyu Xie
2023-06-16 5:54 ` Hongyu Xie
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=2023061606-hunk-overdraft-8d04@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rdunlap@infradead.org \
--cc=xiehongyu1@kylinos.cn \
--cc=xy521521@gmail.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