mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Daniel Thompson <daniel.thompson@linaro.org>
Cc: Jason Wessel <jason.wessel@windriver.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	kgdb-bugreport@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: kgdb: Replace Jason with Daniel
Date: Tue, 5 Dec 2017 14:09:37 +0000	[thread overview]
Message-ID: <20171205140937.gjwufrlt6eo4y5ll@dell> (raw)
In-Reply-To: <20171205121816.28990-1-daniel.thompson@linaro.org>

On Tue, 05 Dec 2017, Daniel Thompson wrote:

> ... with many, many thanks for Jason for all his hard work.
> 
> Cc: Jason Wessel <jason.wessel@windriver.com>
> Signed-off-by: Daniel Thompson <daniel.thompson@linaro.org>
> ---
> 
> Notes:
>     Over the years Jason has become increasingly hard to get hold off
>     and I think he must now be regarded as inactive.
>     
>     Patches in kgdb-next (mine as it happens) have been there for over a
>     year without a corresponding pull request and a couple of architecture
>     specific kgdb fixes have ended up missing a release cycle (or two) as
>     the architecture maintainer waits for an Acked-by from Jason.
>     
>     In the past I've had to rely on Andrew M. to land my own changes to
>     kgdb and in the v4.14 cycle you'll find my Acked-by on b8347c219649
>     ("x86/debug: Handle warnings before the notifier chain, to fix KGDB
>     crash"). That I was sharing surrogate acks convinced me we need a
>     change here and I've offered Jason help via private e-mail without
>     reply.
>     
>     So, I really would prefer it it if this patch listed me as a
>     co-maintainer or, failing that, as least had Jason's blessing... but
>     it doesn't. I certainly suggest this patch takes a long time in
>     review, and if it doesn't attract Jason's attention then I can only
>     reiterate what is says in the commit log: Thanks Jason!
> 
>  MAINTAINERS | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)

It looks like Jason has been inactive in all aspects of upstream
maintainership and as a contributor for well over a year now.

I strongly support the move to make Daniel KGDB Maintainer:

  Acked-by: Lee Jones <lee.jones@linaro.org>

(NB: If this patch does not receive any opposition by the end of this
cycle, it would be my pleasure to take it through one of my trees.) 

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

  reply	other threads:[~2017-12-05 14:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-05 12:18 Daniel Thompson
2017-12-05 14:09 ` Lee Jones [this message]
2017-12-05 14:37   ` [Kgdb-bugreport] " Jason Wessel
2017-12-05 14:44     ` Lee Jones
2017-12-05 14:55     ` Daniel Thompson
2017-12-05 16:42       ` Randy Dunlap
2017-12-06 22:51         ` Jason Wessel

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=20171205140937.gjwufrlt6eo4y5ll@dell \
    --to=lee.jones@linaro.org \
    --cc=akpm@linux-foundation.org \
    --cc=daniel.thompson@linaro.org \
    --cc=jason.wessel@windriver.com \
    --cc=kgdb-bugreport@lists.sourceforge.net \
    --cc=linux-kernel@vger.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

all inboxes | Powered by JetHome®