From: Jim Gill <jgill@vmware.com>
To: Julian Calaby <julian.calaby@gmail.com>, Joe Perches <joe@perches.com>
Cc: Arvind Kumar <arvindkumar@vmware.com>,
"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 17:44:59 +0000 [thread overview]
Message-ID: <A8B2C362-17B7-40ED-B71F-7A1868D9A080@vmware.com> (raw)
In-Reply-To: <CAGRGNgXGxFdzE4fdEzr2iPRX0DPN9JNZcC8HNTt-jW6iNyMqnQ@mail.gmail.com>
On 6/16/16, 8:11 PM, "Julian Calaby" <julian.calaby@gmail.com> wrote:
>[]
>
>>>On Fri, Jun 17, 2016 at 12:33 PM, Joe Perches <joe@perches.com> wrote:
>> []
>>The question to me is whether or not Jim Gill is
>> taking over the maintainership of the entire
>> VMware PVSCSI driver or just a few files of it.
>
>As I see it, he's taking over maintainership of all of it: it's only
>files are drivers/scsi/vmw_pvscsi.[ch] AFAIK.
This is correct, I am taking over maintainership of the entire vmw_pvscsi driver.
next prev parent reply other threads:[~2016-06-17 17:45 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
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 [this message]
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=A8B2C362-17B7-40ED-B71F-7A1868D9A080@vmware.com \
--to=jgill@vmware.com \
--cc=arvindkumar@vmware.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=joe@perches.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;
as well as URLs for NNTP newsgroup(s).