public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: Joe Perches <joe@perches.com>,
	linux-kernel@vger.kernel.org, kexec@lists.infradead.org,
	Haren Myneni <hbabu@us.ibm.com>, Dave Young <dyoung@redhat.com>,
	Baoquan He <bhe@redhat.com>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] MAINTAINERS: Kdump maintainers update
Date: Thu, 26 May 2016 11:07:04 +0900	[thread overview]
Message-ID: <20160526020704.GD18393@verge.net.au> (raw)
In-Reply-To: <20160525133713.GA2590@redhat.com>

On Wed, May 25, 2016 at 09:37:13AM -0400, Vivek Goyal wrote:
> On Wed, May 25, 2016 at 06:24:10AM -0700, Joe Perches wrote:
> > On Wed, 2016-05-25 at 09:16 -0400, Vivek Goyal wrote:
> > > I am proposing following updates to kdump maintainership. I have got
> > > busy in other things and not getting time to spend on kdump. 
> > > 
> > > Removed Haren Myneni as he has not participated in kdump development for
> > > a long time now.
> > > 
> > > Proposing adding the names of Dave and Baoquan as kdump maintainers as
> > > they have been contributing to kdump for a long time now and they are in
> > > a much better position to spend time on this than me.
> > []
> > > diff --git a/MAINTAINERS b/MAINTAINERS
> > []
> > > @@ -6189,8 +6189,9 @@ F:	Documentation/kbuild/kconfig-language.txt
> > >  F:	scripts/kconfig/
> > >  
> > >  KDUMP
> > > +M:	Dave Young <dyoung@redhat.com>
> > > +M:	Baoquan He <bhe@redhat.com>
> > >  M:	Vivek Goyal <vgoyal@redhat.com>
> > 
> > You could mark yourself as an "R:" reviewer
> > instead of an "M:" maintainer.
> 
> That's a good idea. I updated the patch and marked myself reviewer.
> 
> Removed Haren Myneni as he has not participated in kdump development for
> a long time now.
> 
> Proposing adding the names of Dave and Baoquan as kdump maintainers as
> they have been working on it for quite some time on it upstream and
> they are in a much better position to spend time on this than me.
> 
> Signed-off-by: Vivek Goyal <vgoyal@redhat.com>

FWIW I am fine with this change.

Acked-by: Simon Horman <horms@verge.net.au>

> ---
>  MAINTAINERS | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 9c567a4..5792ec2 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -6189,8 +6189,9 @@ F:	Documentation/kbuild/kconfig-language.txt
>  F:	scripts/kconfig/
>  
>  KDUMP
> -M:	Vivek Goyal <vgoyal@redhat.com>
> -M:	Haren Myneni <hbabu@us.ibm.com>
> +M:	Dave Young <dyoung@redhat.com>
> +M:	Baoquan He <bhe@redhat.com>
> +R:	Vivek Goyal <vgoyal@redhat.com>
>  L:	kexec@lists.infradead.org
>  W:	http://lse.sourceforge.net/kdump/
>  S:	Maintained
> -- 
> 2.7.4
> 

  reply	other threads:[~2016-05-26  2:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-25 13:16 [PATCH] MAINTAINERS: Kdump maintainers update Vivek Goyal
2016-05-25 13:24 ` Joe Perches
2016-05-25 13:37   ` Vivek Goyal
2016-05-26  2:07     ` Simon Horman [this message]
2016-05-26  2:29     ` Dave Young

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=20160526020704.GD18393@verge.net.au \
    --to=horms@verge.net.au \
    --cc=akpm@linux-foundation.org \
    --cc=bhe@redhat.com \
    --cc=dyoung@redhat.com \
    --cc=ebiederm@xmission.com \
    --cc=hbabu@us.ibm.com \
    --cc=joe@perches.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vgoyal@redhat.com \
    /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