From: Douglas Anderson <dianders@chromium.org>
To: Jason Wessel <jason.wessel@windriver.com>,
Daniel Thompson <daniel.thompson@linaro.org>
Cc: Christophe Leroy <christophe.leroy@c-s.fr>,
Will Deacon <will@kernel.org>,
kgdb-bugreport@lists.sourceforge.net,
Greg KH <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org,
"Gustavo A . R . Silva" <gustavo@embeddedor.com>,
Douglas Anderson <dianders@chromium.org>,
"David S. Miller" <davem@davemloft.net>,
Rob Herring <robh@kernel.org>,
Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Nicolas Ferre <nicolas.ferre@microchip.com>
Subject: [PATCH] MAINTAINERS: kgdb: Add myself as a reviewer for kgdb/kdb
Date: Fri, 20 Sep 2019 10:44:47 -0700 [thread overview]
Message-ID: <20190920104404.1.I237e68e8825e2d6ac26f8e847f521fe2fcc3705a@changeid> (raw)
I'm interested in kdb / kgdb and have sent various fixes over the
years. I'd like to get CCed on patches so I can be aware of them and
also help review.
Signed-off-by: Douglas Anderson <dianders@chromium.org>
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index c740cf3f93ef..d243c70fc8ce 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -9052,6 +9052,7 @@ F: security/keys/
KGDB / KDB /debug_core
M: Jason Wessel <jason.wessel@windriver.com>
M: Daniel Thompson <daniel.thompson@linaro.org>
+R: Douglas Anderson <dianders@chromium.org>
W: http://kgdb.wiki.kernel.org/
L: kgdb-bugreport@lists.sourceforge.net
T: git git://git.kernel.org/pub/scm/linux/kernel/git/jwessel/kgdb.git
--
2.23.0.351.gc4317032e6-goog
next reply other threads:[~2019-09-20 17:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 17:44 Douglas Anderson [this message]
2019-09-21 5:07 ` [PATCH] MAINTAINERS: kgdb: Add myself as a reviewer for kgdb/kdb Greg KH
2019-09-22 11:57 ` Daniel Thompson
2019-09-22 20:28 ` Will Deacon
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=20190920104404.1.I237e68e8825e2d6ac26f8e847f521fe2fcc3705a@changeid \
--to=dianders@chromium.org \
--cc=christophe.leroy@c-s.fr \
--cc=daniel.thompson@linaro.org \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=gustavo@embeddedor.com \
--cc=jason.wessel@windriver.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=robh@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.