All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Alok Kataria <akataria@vmware.com>
Cc: the arch/x86 maintainers <x86@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	virtualization@lists.linux-foundation.org,
	Doug Covelli <dcovelli@vmware.com>, Ingo Molnar <mingo@elte.hu>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] Add an entry in MAINTAINERS for VMware's hypervisor interface
Date: Wed, 04 Sep 2013 04:45:34 -0700	[thread overview]
Message-ID: <52271D5E.4060402@zytor.com> (raw)
In-Reply-To: <1378284821.9739.7404.camel@akataria-dtop.eng.vmware.com>

On 09/04/2013 01:53 AM, Alok Kataria wrote:
> Hey,
> 
> This change adds an entry to the maintainers file to explicitly state
> that any changes to vmware.c should be sent to the authors of the file
> as well.
> 
> If you are thinking why do this now, off late we have seen quite a few
> changes that touched the "arch/x86/kernel/cpu/vmware.c" file but were
> not directed to me, someone else made me aware of those changes. It
> could be that my use of different SOB lines "Alok N Kataria" vs "Alok
> Kataria" confuses get_maintainer.pl, but adding this entry in
> MAINTAINERS should solve the problem at hand. For one of the changes
> [1], I did verify that get_maintainer.pl, now expectedly includes me in
> the cc list.
> 
> Thanks,
> Alok 
> 

That is indeed what the maintainers file is for.

> Add an entry in MAINTAINERS file to reflect the authors of a file.

No, it reflects the *maintainer(s)* of a file.

	-hpa

WARNING: multiple messages have this Message-ID (diff)
From: "H. Peter Anvin" <hpa@zytor.com>
To: Alok Kataria <akataria@vmware.com>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
	the arch/x86 maintainers <x86@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Doug Covelli <dcovelli@vmware.com>,
	virtualization@lists.linux-foundation.org
Subject: Re: [PATCH] Add an entry in MAINTAINERS for VMware's hypervisor interface
Date: Wed, 04 Sep 2013 04:45:34 -0700	[thread overview]
Message-ID: <52271D5E.4060402@zytor.com> (raw)
In-Reply-To: <1378284821.9739.7404.camel@akataria-dtop.eng.vmware.com>

On 09/04/2013 01:53 AM, Alok Kataria wrote:
> Hey,
> 
> This change adds an entry to the maintainers file to explicitly state
> that any changes to vmware.c should be sent to the authors of the file
> as well.
> 
> If you are thinking why do this now, off late we have seen quite a few
> changes that touched the "arch/x86/kernel/cpu/vmware.c" file but were
> not directed to me, someone else made me aware of those changes. It
> could be that my use of different SOB lines "Alok N Kataria" vs "Alok
> Kataria" confuses get_maintainer.pl, but adding this entry in
> MAINTAINERS should solve the problem at hand. For one of the changes
> [1], I did verify that get_maintainer.pl, now expectedly includes me in
> the cc list.
> 
> Thanks,
> Alok 
> 

That is indeed what the maintainers file is for.

> Add an entry in MAINTAINERS file to reflect the authors of a file.

No, it reflects the *maintainer(s)* of a file.

	-hpa


  reply	other threads:[~2013-09-04 11:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-04  8:53 [PATCH] Add an entry in MAINTAINERS for VMware's hypervisor interface Alok Kataria
2013-09-04  8:53 ` Alok Kataria
2013-09-04 11:45 ` H. Peter Anvin [this message]
2013-09-04 11:45   ` H. Peter Anvin
2013-09-04 11:52 ` [tip:x86/urgent] x86, doc: Add an entry in MAINTAINERS for arch/ x86/kernel/cpu/vmware.c tip-bot for Alok Kataria
2013-09-04 17:16 ` [PATCH] Add an entry in MAINTAINERS for VMware's hypervisor interface Joe Perches
2013-09-04 17:16   ` Joe Perches
2013-09-05  4:46   ` Alok Kataria
2013-09-05  4:46     ` Alok Kataria
2013-09-05  5:03 ` [tip:x86/urgent] x86, doc: Add an entry in MAINTAINERS for arch/ x86/kernel/cpu/vmware.c tip-bot for Alok Kataria

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=52271D5E.4060402@zytor.com \
    --to=hpa@zytor.com \
    --cc=akataria@vmware.com \
    --cc=dcovelli@vmware.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.