From: Peter Foley <pefoley2@verizon.net>
To: "K. Y. Srinivasan" <kys@microsoft.com>
Cc: gregkh@suse.de,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
devel@linuxdriverproject.org, virtualization@lists.osdl.org
Subject: Re: Hyper-V TODO file
Date: Wed, 31 Aug 2011 19:11:39 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.2.00.1108311907130.20924@linux> (raw)
In-Reply-To: <1314829011-28922-1-git-send-email-kys@microsoft.com>
On Wed, 31 Aug 2011, K. Y. Srinivasan wrote:
> Greg, as I have been pestering you for some time now, we are very interested in
> exiting staging and we are willing to dedicate the necessary development
> resources to address whatever issues that may still be pending. So, your help
> in identifying what needs to be done will be greatly appreciated. To that end,
> I think it will be useful to update the TODO file to reflect the current state of
> the drivers. Let us know how we should proceed here.
An issue I've come across in the hyper-v drivers is the forced modular
build. You might want to see if the "depends on m" is still needed.
Thanks,
Peter Foley
next prev parent reply other threads:[~2011-08-31 23:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-31 22:16 Hyper-V TODO file K. Y. Srinivasan
2011-08-31 23:11 ` Peter Foley [this message]
2011-09-01 20:31 ` Greg KH
2011-09-02 14:09 ` KY Srinivasan
2011-09-02 15:17 ` KY Srinivasan
2011-09-02 16:03 ` Greg KH
2011-09-01 20:27 ` Greg KH
2011-09-01 20:30 ` Greg KH
2011-09-01 21:08 ` KY Srinivasan
2011-09-02 16:09 ` Greg KH
2011-09-02 19:47 ` KY Srinivasan
2011-09-02 19:58 ` Greg KH
2011-09-02 20:54 ` KY Srinivasan
2011-09-01 20:57 ` KY Srinivasan
2011-09-22 16:17 K. Y. Srinivasan
2011-09-22 16:05 ` Joe Perches
2011-09-22 17:04 ` Greg KH
2011-09-22 17:20 ` KY Srinivasan
2011-09-22 17:36 ` Greg KH
2011-09-22 18:22 ` KY Srinivasan
2011-10-04 13:59 ` KY Srinivasan
2011-10-04 17:04 ` Greg KH
2011-10-04 17:23 ` 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.LNX.2.00.1108311907130.20924@linux \
--to=pefoley2@verizon.net \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@suse.de \
--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).