The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Rajneesh Bhardwaj <rajneesh.bhardwaj@linux.intel.com>,
	platform-driver-x86@vger.kernel.org
Cc: dvhart@infradead.org, andy@infradead.org,
	linux-kernel@vger.kernel.org, rajneesh.bhardwaj@intel.com,
	david.e.box@linux.intel.com
Subject: Re: [Patch v2] MAINTAINERS: intel_telemetry: Update maintainers info
Date: Tue, 09 Oct 2018 10:46:56 -0700	[thread overview]
Message-ID: <262d8a05cedc76bc90fa5be7d3b92d5faa2b4ce9.camel@perches.com> (raw)
In-Reply-To: <20181009141833.25972-1-rajneesh.bhardwaj@linux.intel.com>

On Tue, 2018-10-09 at 19:48 +0530, Rajneesh Bhardwaj wrote:
> Add myself and David as the new maintainers for Intel Telemetry driver
> since Souvik no longer works with Intel. David and I work on power
> management and debug related drivers which are pretty close to this one
> in terms of functionalities so volunteering for the task.
> 
> Signed-off-by: Box, David E <david.e.box@linux.intel.com>
> Signed-off-by: Rajneesh Bhardwaj <rajneesh.bhardwaj@linux.intel.com>
> ---
>  MAINTAINERS | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 22065048d89d..f33ebd1b8034 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -7530,7 +7530,8 @@ F:	arch/x86/crypto/sha*-mb/
>  F:	crypto/mcryptd.c
>  
>  INTEL TELEMETRY DRIVER
> -M:	Souvik Kumar Chakravarty <souvik.k.chakravarty@intel.com>
> +M:	Rajneesh Bhardwaj <rajneesh.bhardwaj@linux.intel.com>
> +M:	Box, David E <david.e.box@linux.intel.com>

It is better to quote your name when it uses
non-alphabetic characters like periods and commas.

Especially the comma because that is commonly used
by email clients as a multiple address separator so
it makes copy/paste use error-prone.

It's also likely better to use a more typical
"First <Initial> Last" name style. 

>  L:	platform-driver-x86@vger.kernel.org
>  S:	Maintained
>  F:	arch/x86/include/asm/intel_telemetry.hch mor


  reply	other threads:[~2018-10-09 17:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-09 14:18 [Patch v2] MAINTAINERS: intel_telemetry: Update maintainers info Rajneesh Bhardwaj
2018-10-09 17:46 ` Joe Perches [this message]
2018-10-12 16:28   ` [PATCH V3] " David E. Box
2018-10-12 16:46     ` Joe Perches
2018-10-16 15:51       ` Andy Shevchenko
2018-10-19 14:02         ` Andy Shevchenko
2018-10-19 14:02     ` Andy Shevchenko

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=262d8a05cedc76bc90fa5be7d3b92d5faa2b4ce9.camel@perches.com \
    --to=joe@perches.com \
    --cc=andy@infradead.org \
    --cc=david.e.box@linux.intel.com \
    --cc=dvhart@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=rajneesh.bhardwaj@intel.com \
    --cc=rajneesh.bhardwaj@linux.intel.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