From: Thomas Gleixner <tglx@linutronix.de>
To: KY Srinivasan <kys@microsoft.com>
Cc: Christoph Hellwig <hch@infradead.org>,
"johnstul@us.ibm.com" <johnstul@us.ibm.com>,
"gregkh@suse.de" <gregkh@suse.de>,
"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: vmbus driver
Date: Mon, 23 May 2011 15:51:30 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.02.1105231550360.3078@ionos> (raw)
In-Reply-To: <6E21E5352C11B742B20C142EB499E0481FC6DF@TK5EX14MBXC122.redmond.corp.microsoft.com>
On Mon, 23 May 2011, KY Srinivasan wrote:
> I am working on getting Hyper-V drivers (drivers/staging/hv/*) out of staging.
> I would like to request you to look at the Hyper-V timesource driver:
> drivers/staging/hv/hv_timesource.c. The supporting code for this driver
> is already part of the base kernel. Let me know if this driver is ready to exit staging.
Can you please send a patch against drivers/clocksource (the staging
part is uninteresting for review).
Thanks,
tglx
next prev parent reply other threads:[~2011-05-23 13:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-19 22:06 vmbus driver K. Y. Srinivasan
2011-05-20 12:26 ` Christoph Hellwig
2011-05-20 13:12 ` KY Srinivasan
2011-05-20 13:22 ` Christoph Hellwig
2011-05-20 14:08 ` KY Srinivasan
2011-05-20 13:36 ` KY Srinivasan
2011-05-22 10:59 ` Christoph Hellwig
2011-05-22 17:32 ` KY Srinivasan
2011-05-23 12:54 ` KY Srinivasan
2011-05-23 13:51 ` Thomas Gleixner [this message]
2011-05-23 16:16 ` KY Srinivasan
2011-05-20 13:05 ` Greg KH
2011-05-20 13:21 ` 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=alpine.LFD.2.02.1105231550360.3078@ionos \
--to=tglx@linutronix.de \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@suse.de \
--cc=hch@infradead.org \
--cc=johnstul@us.ibm.com \
--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 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).