From: Greg KH <gregkh@suse.de>
To: KY Srinivasan <kys@microsoft.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"virtualization@lists.osdl.org" <virtualization@lists.osdl.org>
Subject: Re: Hyper-V vmbus driver
Date: Mon, 11 Apr 2011 12:07:08 -0700 [thread overview]
Message-ID: <20110411190708.GA21355@suse.de> (raw)
In-Reply-To: <6E21E5352C11B742B20C142EB499E0481C8D35@TK5EX14MBXC126.redmond.corp.microsoft.com>
On Mon, Apr 11, 2011 at 06:46:24PM +0000, KY Srinivasan wrote:
> Greg,
>
>
>
> Recently, you applied a patch-set from me that cleaned a bunch of architectural
> issues in the vmbus driver.
>
> With that patch-set, I think I have addressed all architectural issues that I
> am aware of.
>
> I was wondering if you would have the time to let me know what else would have
> to be addressed
>
> in the vmbus driver, before it could be considered ready for exiting staging.
> As always your help is
>
> greatly appreciated.
Hm, interesting word wrapping there, might I consider a "real" email
client one of these days? :)
Anyway, yes, I discussed this with Hank last week at the LF Collab
summit. I'll look at the vmbus code later this week when I catch up on
all of my other work (stable, usb, tty, staging, etc.) that has piled up
during my 2 week absence, and get back to you with what I feel is still
needed to be done, if anything.
thanks,
greg k-h
next prev parent reply other threads:[~2011-04-11 19:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 18:46 Hyper-V vmbus driver KY Srinivasan
2011-04-11 19:07 ` Greg KH [this message]
2011-04-11 19:51 ` KY Srinivasan
2011-04-23 15:20 ` Greg KH
2011-04-23 15:20 ` Greg KH
2011-04-24 16:18 ` KY Srinivasan
2011-04-25 0:13 ` Greg KH
2011-04-25 2:15 ` KY Srinivasan
2011-04-25 3:03 ` Greg KH
2011-04-25 3:03 ` Greg KH
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=20110411190708.GA21355@suse.de \
--to=gregkh@suse.de \
--cc=devel@linuxdriverproject.org \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.osdl.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.