From: Greg KH <gregkh@linuxfoundation.org>
To: Daniel Thompson <daniel.thompson@linaro.org>
Cc: Sumit Garg <sumit.garg@linaro.org>,
kgdb-bugreport@lists.sourceforge.net, jason.wessel@windriver.com,
dianders@chromium.org, pmladek@suse.com,
sergey.senozhatsky@gmail.com, jslaby@suse.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 4/4] kdb: Switch to use safer dbg_io_ops over console APIs
Date: Fri, 26 Jun 2020 16:19:32 +0200 [thread overview]
Message-ID: <20200626141932.GC4141629@kroah.com> (raw)
In-Reply-To: <20200626121348.eeutt4py34f2yg3y@holly.lan>
On Fri, Jun 26, 2020 at 01:13:48PM +0100, Daniel Thompson wrote:
> Hi Greg
>
> This patch touches some kgdb related code in both serial and usb trees.
>
> Any objections to my queuing this via the kgdb tree?
>
> After testing I've concluded that this, and its friends (which only
> touch kgdb), fix enough problems that I plan to queue it for v5.8.
No objections at all:
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
next prev parent reply other threads:[~2020-06-26 14:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-04 10:01 [PATCH v6 0/4] kdb: Improve console handling Sumit Garg
2020-06-04 10:01 ` [PATCH v6 1/4] kdb: Re-factor kdb_printf() message write code Sumit Garg
2020-06-04 10:01 ` [PATCH v6 2/4] kdb: Check status of console prior to invoking handlers Sumit Garg
2020-06-04 10:01 ` [PATCH v6 3/4] kdb: Make kdb_printf() console handling more robust Sumit Garg
2020-06-04 10:01 ` [PATCH v6 4/4] kdb: Switch to use safer dbg_io_ops over console APIs Sumit Garg
2020-06-04 21:12 ` Doug Anderson
2020-06-05 9:53 ` Petr Mladek
2020-06-26 12:13 ` Daniel Thompson
2020-06-26 14:19 ` Greg KH [this message]
2020-06-05 3:57 ` [PATCH v6 0/4] kdb: Improve console handling Sergey Senozhatsky
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=20200626141932.GC4141629@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=daniel.thompson@linaro.org \
--cc=dianders@chromium.org \
--cc=jason.wessel@windriver.com \
--cc=jslaby@suse.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=sergey.senozhatsky@gmail.com \
--cc=sumit.garg@linaro.org \
/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