From: "K. Y. Srinivasan" <kys@microsoft.com>
To: gregkh@suse.de, linux-kernel@vger.kernel.org,
devel@linuxdriverproject.org, virtualization@lists.osdl.org
Subject: Hyper-V driver patches
Date: Thu, 11 Aug 2011 17:09:45 -0700 [thread overview]
Message-ID: <1313107785-13318-1-git-send-email-kys@microsoft.com> (raw)
Greg,
Some weeks ago, I had sent out a fairly large patch-set for your consideration.
I know you are very busy; however, I am getting a little nervous since I have
not heard from you. Please let me know if I should resend these patches.
In addition to this one large patch-set, we have also sent a
bunch of other patches as well. I just want to make sure that these
patches are still in your queue.
On a different note, with these patches I have addressed all the review
comments that I have gotten from you, Christoph and others.
I was wondering if you would have the time to let me
know what else would have to be done to get the vmbus driver out of staging.
Regards,
K. Y
next reply other threads:[~2011-08-11 23:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-12 0:09 K. Y. Srinivasan [this message]
2011-08-12 17:50 ` Hyper-V driver patches Greg KH
2011-08-12 21:24 ` Greg KH
2011-08-12 21:26 ` 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=1313107785-13318-1-git-send-email-kys@microsoft.com \
--to=kys@microsoft.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox