From: Arvind Kumar <arvindkumar@vmware.com>
To: Julian Calaby <julian.calaby@gmail.com>, Jim Gill <jgill@vmware.com>
Cc: "jejb@linux.vnet.ibm.com" <jejb@linux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
"pv-drivers@vmware.com" <pv-drivers@vmware.com>,
linux-scsi <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] VMW_PVSCSI: Change to update maintainer details (name, email)
Date: Fri, 17 Jun 2016 02:03:59 +0000 [thread overview]
Message-ID: <1466128907097.81812@vmware.com> (raw)
In-Reply-To: <CAGRGNgVK_xMmCQFHhhJ9E1frzTE--ivX1Po19O_qUjgYtuUK7A@mail.gmail.com>
Hi Julian,
Thanks for spotting that. We will update that too.
I don't really see it as redundant rather as a quick reference instead of digging out the MAINTAINERS file and then search for vmw_pvscsi.c file. Specially for those readers who might not even know about the MAINTAINERS file.
Thanks!
Arvind
________________________________________
From: Julian Calaby <julian.calaby@gmail.com>
Sent: Thursday, June 16, 2016 6:48 PM
To: Jim Gill
Cc: jejb@linux.vnet.ibm.com; Martin K. Petersen; Arvind Kumar; pv-drivers@vmware.com; linux-scsi; linux-kernel@vger.kernel.org
Subject: Re: [PATCH] VMW_PVSCSI: Change to update maintainer details (name, email)
Hi Jim,
On Fri, Jun 17, 2016 at 11:05 AM, Jim Gill <jgill@vmware.com> wrote:
> From 6a076cc00ec12c6f9cba58ee7e4c3dec49e1e7e5 Mon Sep 17 00:00:00 2001
> From: Jim Gill <jgill@vmware.com>
> Date: Thu, 16 Jun 2016 14:10:43 -0700
> Subject: [PATCH] VMW_PVSCSI: Change to update maintainer details (name,
> email)
>
> Signed-off-by: Jim Gill <jgill@vmware.com>
> ---
> drivers/scsi/vmw_pvscsi.c | 2 +-
> drivers/scsi/vmw_pvscsi.h | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/scsi/vmw_pvscsi.c b/drivers/scsi/vmw_pvscsi.c
> index 6164634..4a0d3cd 100644
> --- a/drivers/scsi/vmw_pvscsi.c
> +++ b/drivers/scsi/vmw_pvscsi.c
> @@ -17,7 +17,7 @@
> * along with this program; if not, write to the Free Software
> * Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301
> USA.
> *
> - * Maintained by: Arvind Kumar <arvindkumar@vmware.com>
> + * Maintained by: Jim Gill <jgill@vmware.com>
Shouldn't you update MAINTAINERs too? And isn't having this
information in these files redundant?
Thanks,
--
Julian Calaby
Email: julian.calaby@gmail.com
Profile: https://urldefense.proofpoint.com/v2/url?u=http-3A__www.google.com_profiles_julian.calaby_&d=CwIBaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=bUMaNc7nC9xbXtaMJrOvIIPNpPH0chY2kdRsskQn6GY&m=JibRIMgSBQLffjc5PofQnpJ0k_gawmvafvIKpsEaMzk&s=CeVpY1FwvY9Qlb0VDeQUXeeL3kuVkcIKTZIC7exS6SM&e=
next prev parent reply other threads:[~2016-06-17 2:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 1:05 [PATCH] VMW_PVSCSI: Change to update maintainer details (name, email) Jim Gill
2016-06-17 1:19 ` Arvind Kumar
2016-06-17 1:48 ` Julian Calaby
2016-06-17 2:03 ` Arvind Kumar [this message]
2016-06-17 2:18 ` Julian Calaby
2016-06-17 2:33 ` Joe Perches
2016-06-17 2:44 ` Julian Calaby
2016-06-17 3:04 ` Joe Perches
2016-06-17 3:11 ` Julian Calaby
2016-06-17 7:55 ` [Pv-drivers] " Thomas Hellstrom
2016-06-17 17:44 ` Jim Gill
2016-06-17 18:06 ` Joe Perches
2016-06-17 18:16 ` Jim Gill
2016-06-21 2:01 ` Martin K. Petersen
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=1466128907097.81812@vmware.com \
--to=arvindkumar@vmware.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=jgill@vmware.com \
--cc=julian.calaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=pv-drivers@vmware.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