From: Douglas Anderson <dianders@chromium.org>
To: Paul Burton <paul.burton@mips.com>,
Jason Wessel <jason.wessel@windriver.com>,
Daniel Thompson <daniel.thompson@linaro.org>
Cc: qiaochong@loongson.cn, kgdb-bugreport@lists.sourceforge.net,
ralf@linux-mips.org, "Douglas Anderson" <dianders@chromium.org>,
"Mike Rapoport" <rppt@linux.ibm.com>,
"Chuhong Yuan" <hslester96@gmail.com>,
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>,
"Andrew Morton" <akpm@linux-foundation.org>,
"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>,
linux-kernel@vger.kernel.org,
"Dan Carpenter" <dan.carpenter@oracle.com>
Subject: [PATCH 0/5] kdb: Don't implicitly change tasks; plus misc fixups
Date: Sat, 9 Nov 2019 11:16:39 -0800 [thread overview]
Message-ID: <20191109191644.191766-1-dianders@chromium.org> (raw)
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(-)
--
2.24.0.432.g9d3f5f5b63-goog
next reply other threads:[~2019-11-09 19:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-09 19:16 Douglas Anderson [this message]
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
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
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=20191109191644.191766-1-dianders@chromium.org \
--to=dianders@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=bigeasy@linutronix.de \
--cc=christophe.leroy@c-s.fr \
--cc=dan.carpenter@oracle.com \
--cc=daniel.thompson@linaro.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).