From: "Denis V. Lunev" <den@openvz.org>
To: KY Srinivasan <kys@microsoft.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"olaf@aepfle.de" <olaf@aepfle.de>,
"apw@canonical.com" <apw@canonical.com>,
"vkuznets@redhat.com" <vkuznets@redhat.com>,
"jasowang@redhat.com" <jasowang@redhat.com>
Cc: Andrey Smetanin <asmetanin@virtuozzo.com>,
Haiyang Zhang <haiyangz@microsoft.com>
Subject: Re: [PATCH 07/10] drivers/hv: cleanup synic msrs if vmbus connect failed
Date: Thu, 8 Oct 2015 20:31:41 +0300 [thread overview]
Message-ID: <5616A87D.8080607@openvz.org> (raw)
In-Reply-To: <SN1PR0301MB166280D8C0DB666860885019A0350@SN1PR0301MB1662.namprd03.prod.outlook.com>
On 10/08/2015 08:28 PM, KY Srinivasan wrote:
>
>> -----Original Message-----
>> From: Denis V. Lunev [mailto:den@openvz.org]
>> Sent: Thursday, October 8, 2015 10:20 AM
>> To: KY Srinivasan <kys@microsoft.com>; gregkh@linuxfoundation.org; linux-
>> kernel@vger.kernel.org; devel@linuxdriverproject.org; olaf@aepfle.de;
>> apw@canonical.com; vkuznets@redhat.com; jasowang@redhat.com
>> Cc: Andrey Smetanin <asmetanin@virtuozzo.com>; Haiyang Zhang
>> <haiyangz@microsoft.com>
>> Subject: Re: [PATCH 07/10] drivers/hv: cleanup synic msrs if vmbus connect
>> failed
>>
>> On 10/08/2015 05:01 AM, K. Y. Srinivasan wrote:
>>> From: Denis V. Lunev <den@openvz.org>
>> K.Y.,
>>
>> there is one subtle thing in this submission. You have changed "From:"
>> field in comparison with the original letter. I have submitted
>> the patch with "From: Andrey Smetanin <asmetanin@virtuozzo.com>"
>> In this case Author: in the resulted git mainstream commit will
>> be Andrey. With your submission the resulted Author will be I.
>>
>> This was already happened once with
>>
>> commit cc2dd4027a43bb36c846f195a764edabc0828602
>> Author: Denis V. Lunev <den@openvz.org>
>> Date: Sat Aug 1 16:08:20 2015 -0700
>>
>> mshyperv: fix recognition of Hyper-V guest crash MSR's
>>
>> The situation looks a bit unfair.
>>
>> Can we do something with that now/next time?
> I am going to be resubmitting this series. I will fix it up.
thank you very much :)
Den
next prev parent reply other threads:[~2015-10-08 17:31 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-08 1:59 [PATCH 00/10] Drivers: hv: Miscellaneous fixes K. Y. Srinivasan
2015-10-08 2:01 ` [PATCH 01/10] Drivers: hv: util: Increase the timeout for util services K. Y. Srinivasan
2015-10-08 2:01 ` [PATCH 02/10] Drivers: hv: utils: run polling callback always in interrupt context K. Y. Srinivasan
2015-10-08 13:24 ` Vitaly Kuznetsov
2015-10-08 13:30 ` Olaf Hering
2015-10-08 13:52 ` Vitaly Kuznetsov
2015-10-08 14:55 ` KY Srinivasan
2015-10-09 7:07 ` Olaf Hering
2015-10-09 10:13 ` Vitaly Kuznetsov
2015-10-09 11:28 ` Olaf Hering
2015-10-12 6:05 ` KY Srinivasan
2015-10-13 9:46 ` Olaf Hering
2015-10-13 21:33 ` KY Srinivasan
2015-10-08 2:01 ` [PATCH 03/10] tools: hv: report ENOSPC errors in hv_fcopy_daemon K. Y. Srinivasan
2015-10-08 2:01 ` [PATCH 04/10] tools: hv: remove repeated HV_FCOPY string K. Y. Srinivasan
2015-10-08 2:01 ` [PATCH 05/10] Drivers: hv: util: catch allocation errors K. Y. Srinivasan
2015-10-08 2:01 ` [PATCH 06/10] Drivers: hv: utils: use memdup_user in hvt_op_write K. Y. Srinivasan
2015-10-08 2:01 ` [PATCH 07/10] drivers/hv: cleanup synic msrs if vmbus connect failed K. Y. Srinivasan
2015-10-08 17:19 ` Denis V. Lunev
2015-10-08 17:28 ` KY Srinivasan
2015-10-08 17:31 ` Denis V. Lunev [this message]
2015-10-08 2:01 ` [PATCH 08/10] drivers:hv: Export a function that maps Linux CPU num onto Hyper-V proc num K. Y. Srinivasan
2015-10-08 2:01 ` [PATCH 09/10] drivers:hv: Export the API to invoke a hypercall on Hyper-V K. Y. Srinivasan
2015-10-08 2:01 ` [PATCH 10/10] drivers:hv: Define the channel type for Hyper-V PCI Express pass-through K. Y. Srinivasan
2015-10-08 10:24 ` Vitaly Kuznetsov
2015-10-08 13:23 ` [PATCH 01/10] Drivers: hv: util: Increase the timeout for util services Olaf Hering
2015-10-08 14:40 ` KY Srinivasan
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=5616A87D.8080607@openvz.org \
--to=den@openvz.org \
--cc=apw@canonical.com \
--cc=asmetanin@virtuozzo.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=haiyangz@microsoft.com \
--cc=jasowang@redhat.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf@aepfle.de \
--cc=vkuznets@redhat.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).