From: Daniel Thompson <daniel.thompson@linaro.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Doug Anderson" <dianders@chromium.org>,
"Paul Burton" <paul.burton@mips.com>,
"Jason Wessel" <jason.wessel@windriver.com>,
qiaochong <qiaochong@loongson.cn>,
kgdb-bugreport@lists.sourceforge.net,
"Ralf Baechle" <ralf@linux-mips.org>,
"Mike Rapoport" <rppt@linux.ibm.com>,
"Chuhong Yuan" <hslester96@gmail.com>,
linux-mips <linux-mips@vger.kernel.org>,
"Nicholas Mc Guire" <hofrat@osadl.org>,
"James Hogan" <jhogan@kernel.org>,
"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
"Serge Semin" <fancer.lancer@gmail.com>,
"Prarit Bhargava" <prarit@redhat.com>,
"Will Deacon" <will@kernel.org>,
"Sebastian Andrzej Siewior" <bigeasy@linutronix.de>,
"Christophe Leroy" <christophe.leroy@c-s.fr>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
LKML <linux-kernel@vger.kernel.org>,
"Dan Carpenter" <dan.carpenter@oracle.com>
Subject: Re: [PATCH 0/5] kdb: Don't implicitly change tasks; plus misc fixups
Date: Wed, 29 Jan 2020 15:23:40 +0000 [thread overview]
Message-ID: <20200129152340.bjlzlrybkujfdf5l@holly.lan> (raw)
In-Reply-To: <20200128174248.756f18d713e759be2b4273db@linux-foundation.org>
On Tue, Jan 28, 2020 at 05:42:48PM -0800, Andrew Morton wrote:
> On Tue, 28 Jan 2020 08:59:01 -0800 Doug Anderson <dianders@chromium.org> wrote:
>
> > Hi
> >
> > On Sat, Nov 9, 2019 at 11:17 AM Douglas Anderson <dianders@chromium.org> wrote:
> > >
> > > This started out as just a follow-up to Daniel's post [1]. I wanted
> > > to stop implicitly changing the current task in kdb. ...but, of
> > > course, everywhere you look in kdb there are things to cleanup, so
> > > this gets a few misc cleanups I found along the way. Enjoy.
> > >
> > > [1] https://lore.kernel.org/r/20191010150735.dhrj3pbjgmjrdpwr@holly.lan
> > >
> > >
> > > Douglas Anderson (5):
> > > MIPS: kdb: Remove old workaround for backtracing on other CPUs
> > > kdb: kdb_current_regs should be private
> > > kdb: kdb_current_task shouldn't be exported
> > > kdb: Gid rid of implicit setting of the current task / regs
> > > kdb: Get rid of confusing diag msg from "rd" if current task has no
> > > regs
> > >
> > > arch/mips/kernel/traps.c | 5 -----
> > > include/linux/kdb.h | 2 --
> > > kernel/debug/kdb/kdb_bt.c | 8 +-------
> > > kernel/debug/kdb/kdb_main.c | 31 ++++++++++++++-----------------
> > > kernel/debug/kdb/kdb_private.h | 2 +-
> > > 5 files changed, 16 insertions(+), 32 deletions(-)
> >
> > I noticed that this series doesn't seem to be in linux-next, but I
> > think it was supposed to target v5.6? Do you know if there is
> > anything outstanding or if it'll be queued up sometime soon?
> >
>
> I grabbed them.
>
> Are there any updates on the testing status, particularly on MIPS?
I put in a fair bit of work earlier this dev cycle to add MIPS to the
kgdb test suite. Unfortunately that left me catching up on a few other
things... or putting it another way I am late putting together the kgdb
tree for v5.6. It will be done by the weekend.
The first patch never got a formal Acked-by from the MIPS folks but they
commented positively so we can probably go ahead.
Daniel.
prev parent reply other threads:[~2020-01-29 15:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-09 19:16 [PATCH 0/5] kdb: Don't implicitly change tasks; plus misc fixups Douglas Anderson
2019-11-09 19:16 ` [PATCH 1/5] MIPS: kdb: Remove old workaround for backtracing on other CPUs Douglas Anderson
2019-11-14 10:51 ` Daniel Thompson
2019-11-14 16:10 ` Doug Anderson
2019-11-15 0:30 ` Paul Burton
2019-11-09 19:16 ` [PATCH 2/5] kdb: kdb_current_regs should be private Douglas Anderson
2019-11-09 19:16 ` [PATCH 3/5] kdb: kdb_current_task shouldn't be exported Douglas Anderson
2019-11-09 19:16 ` [PATCH 4/5] kdb: Gid rid of implicit setting of the current task / regs Douglas Anderson
2019-11-09 19:16 ` [PATCH 5/5] kdb: Get rid of confusing diag msg from "rd" if current task has no regs Douglas Anderson
2020-01-28 16:59 ` [PATCH 0/5] kdb: Don't implicitly change tasks; plus misc fixups Doug Anderson
2020-01-29 1:42 ` Andrew Morton
2020-01-29 15:23 ` Daniel Thompson [this message]
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=20200129152340.bjlzlrybkujfdf5l@holly.lan \
--to=daniel.thompson@linaro.org \
--cc=akpm@linux-foundation.org \
--cc=bigeasy@linutronix.de \
--cc=christophe.leroy@c-s.fr \
--cc=dan.carpenter@oracle.com \
--cc=dianders@chromium.org \
--cc=ebiederm@xmission.com \
--cc=f4bug@amsat.org \
--cc=fancer.lancer@gmail.com \
--cc=gustavo@embeddedor.com \
--cc=hofrat@osadl.org \
--cc=hslester96@gmail.com \
--cc=jason.wessel@windriver.com \
--cc=jhogan@kernel.org \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=paul.burton@mips.com \
--cc=prarit@redhat.com \
--cc=qiaochong@loongson.cn \
--cc=ralf@linux-mips.org \
--cc=rppt@linux.ibm.com \
--cc=will@kernel.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;
as well as URLs for NNTP newsgroup(s).