linux-watchdog.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: "Boylston, Brian" <brian.boylston@hpe.com>
Cc: "linux-watchdog@vger.kernel.org" <linux-watchdog@vger.kernel.org>
Subject: Re: [PATCH] watchdog: hpwdt: update HPE maintainer
Date: Mon, 23 May 2016 13:19:27 -0700	[thread overview]
Message-ID: <20160523201927.GA16193@roeck-us.net> (raw)
In-Reply-To: <CS1PR84MB011968DAA650E6408707CC1A8E4E0@CS1PR84MB0119.NAMPRD84.PROD.OUTLOOK.COM>

On Mon, May 23, 2016 at 07:38:46PM +0000, Boylston, Brian wrote:
> Guenter Roeck wrote on 2016-05-23:
> > Hi Brian,
> > 
> > On 05/23/2016 06:33 AM, Brian Boylston wrote:
> >> Update the HPE maintainer of the hpwdt driver.
> >> 
> >> Signed-off-by: Brian Boylston <brian.boylston@hpe.com>
> > 
> > A driver's maintainer is commonly updated in MAINTAINERS, not in the driver itself.
> > If you are the formal maintainer, I would suggest to add an entry for the driver
> > into the MAINTAINERS file; this would ensure that you get copied on patches
> > affecting the driver.
> 
> Thanks, Guenter.  I'll work on an update to MAINTAINERS.
> Okay if I leave my name out of hpwdt.txt then?
> 
Hi Brian,

hpwdt.txt is irrelevant when it comes to maintainers. In general I would
recommend to not list e-mail addresses in documentation, or anything else that
isn't static, such as the name of a driver maintainer. It just adds another
place which needs to be updated. So, yes, sure it is ok to not mention your
name there. You can list your name if you like, but please not as "current
maintainer".

Thanks,
Guenter

      reply	other threads:[~2016-05-23 20:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-23 13:33 [PATCH] watchdog: hpwdt: update HPE maintainer Brian Boylston
2016-05-23 14:56 ` Guenter Roeck
2016-05-23 19:38   ` Boylston, Brian
2016-05-23 20:19     ` Guenter Roeck [this message]

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=20160523201927.GA16193@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=brian.boylston@hpe.com \
    --cc=linux-watchdog@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;
as well as URLs for NNTP newsgroup(s).