From: Daniel Thompson <daniel.thompson@linaro.org>
To: Douglas Anderson <dianders@chromium.org>
Cc: Jason Wessel <jason.wessel@windriver.com>,
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>,
"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: Re: [PATCH] MAINTAINERS: kgdb: Add myself as a reviewer for kgdb/kdb
Date: Sun, 22 Sep 2019 04:57:58 -0700 [thread overview]
Message-ID: <20190922115758.jbouheoztxkndyvc@holly.lan> (raw)
In-Reply-To: <20190920104404.1.I237e68e8825e2d6ac26f8e847f521fe2fcc3705a@changeid>
On Fri, Sep 20, 2019 at 10:44:47AM -0700, Douglas Anderson wrote:
> 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.
It will be great to have you on board. Actually I was already
contemplating informally pinging you to ask for review some of my clean
ups in the upcoming dev cycle. I'm very happy to make it official
instead!
> Signed-off-by: Douglas Anderson <dianders@chromium.org>
I'll get a PR together for this shortly (busy with travel this week).
In the mean time at least I can offer you a firm:
Acked-by: Daniel Thompson <daniel.thompson@linaro.org>
Daniel.
next prev parent reply other threads:[~2019-09-22 11:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 17:44 [PATCH] MAINTAINERS: kgdb: Add myself as a reviewer for kgdb/kdb Douglas Anderson
2019-09-21 5:07 ` Greg KH
2019-09-22 11:57 ` Daniel Thompson [this message]
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=20190922115758.jbouheoztxkndyvc@holly.lan \
--to=daniel.thompson@linaro.org \
--cc=christophe.leroy@c-s.fr \
--cc=davem@davemloft.net \
--cc=dianders@chromium.org \
--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 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).