From: KY Srinivasan <kys@microsoft.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "apw@canonical.com" <apw@canonical.com>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"olaf@aepfle.de" <olaf@aepfle.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH RESEND 0/6] Drivers: hv: vmbus: Some miscellaneous bug fixes and cleanup
Date: Wed, 4 Feb 2015 00:01:51 +0000 [thread overview]
Message-ID: <BY2PR0301MB0711A5F813E92F7AA54D758BA03A0@BY2PR0301MB0711.namprd03.prod.outlook.com> (raw)
In-Reply-To: <20150204000033.GA24139@kroah.com>
> -----Original Message-----
> From: Greg KH [mailto:gregkh@linuxfoundation.org]
> Sent: Tuesday, February 3, 2015 4:01 PM
> To: KY Srinivasan
> Cc: apw@canonical.com; devel@linuxdriverproject.org; olaf@aepfle.de;
> linux-kernel@vger.kernel.org
> Subject: Re: [PATCH RESEND 0/6] Drivers: hv: vmbus: Some miscellaneous
> bug fixes and cleanup
>
> On Tue, Feb 03, 2015 at 11:51:53PM +0000, KY Srinivasan wrote:
> >
> >
> > > -----Original Message-----
> > > From: Greg KH [mailto:gregkh@linuxfoundation.org]
> > > Sent: Tuesday, February 3, 2015 3:45 PM
> > > To: KY Srinivasan
> > > Cc: linux-kernel@vger.kernel.org; devel@linuxdriverproject.org;
> > > olaf@aepfle.de; apw@canonical.com; vkuznets@redhat.com
> > > Subject: Re: [PATCH RESEND 0/6] Drivers: hv: vmbus: Some
> > > miscellaneous bug fixes and cleanup
> > >
> > > On Tue, Feb 03, 2015 at 07:31:36AM -0800, K. Y. Srinivasan wrote:
> > > > This is a resend of the patches from Dexuan and Nicholas
> > >
> > > What do you mean by "resend"? Did you send them to be before? I
> > > can't see them in my inbox anywhere.
> > >
> > > confused,
> >
> > Greg,
> >
> > You had asked me to resend patches after reviewing them and making
> > sure they applied cleanly. These patches were posted on LKML earlier; I
> resent them.
>
> But I didn't know that, as you hadn't sent them to me before.
>
> Please collect all hyperv patches and send them to me in batches like other
> subsystem maintainers do, it makes it easier for me as I'm obviously easy to
> get confused here...
Will do.
K. Y
>
> thanks,
>
> greg k-h
prev parent reply other threads:[~2015-02-04 0:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-03 15:31 [PATCH RESEND 0/6] Drivers: hv: vmbus: Some miscellaneous bug fixes and cleanup K. Y. Srinivasan
2015-02-03 15:31 ` [PATCH RESEND 1/6] hv: hv_util: move vmbus_open() to a later place K. Y. Srinivasan
2015-02-03 15:31 ` [PATCH RESEND 2/6] hv: vmbus_post_msg: retry the hypercall on some transient errors K. Y. Srinivasan
2015-02-03 15:31 ` [PATCH RESEND 3/6] hv: vmbus_open(): reset the channel state on ENOMEM K. Y. Srinivasan
2015-02-03 15:31 ` [PATCH RESEND 4/6] hv: channel: match var type to return type of wait_for_completion K. Y. Srinivasan
2015-02-03 15:31 ` [PATCH RESEND 5/6] hv: channel_mgmt: " K. Y. Srinivasan
2015-02-03 15:31 ` [PATCH RESEND 6/6] hv: hv_balloon: " K. Y. Srinivasan
2015-02-03 23:45 ` [PATCH RESEND 0/6] Drivers: hv: vmbus: Some miscellaneous bug fixes and cleanup Greg KH
2015-02-03 23:51 ` KY Srinivasan
2015-02-04 0:00 ` Greg KH
2015-02-04 0:01 ` KY Srinivasan [this message]
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=BY2PR0301MB0711A5F813E92F7AA54D758BA03A0@BY2PR0301MB0711.namprd03.prod.outlook.com \
--to=kys@microsoft.com \
--cc=apw@canonical.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf@aepfle.de \
/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).