From: Greg KH <greg@kroah.com>
To: Balbir Singh <balbir@linux.vnet.ibm.com>
Cc: Sam Ramji <sramji@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
linux-kernel@vger.kernel.org, virtualization@lists.osdl.org,
devel@driverdev.osuosl.org, shemminger@linux-foundation.org
Subject: Re: [patch 00/54] [Announce] Microsoft Hyper-V drivers for Linux
Date: Tue, 21 Jul 2009 09:51:53 -0700 [thread overview]
Message-ID: <20090721165153.GG14746@kroah.com> (raw)
In-Reply-To: <20090721110607.GA25127@balbir.in.ibm.com>
On Tue, Jul 21, 2009 at 04:36:07PM +0530, Balbir Singh wrote:
> * Greg Kroah-Hartman <gregkh@suse.de> [2009-07-20 09:00:25]:
>
> >
> > Hi all,
> >
> > I'm happy to announce, that after many months of discussions, Microsoft
> > has released their Hyper-V Linux drivers under the GPLv2. Following
> > this message, will be the patches that add the drivers to the
> > drivers/staging/ tree, and a whole bunch of cleanups.
> >
> > It's taken a long road to get here, and I'd like to thank the following
> > people who made this possible:
> > - Steve Hemminger for the initial prodding and extreme patience
> > - Hank Janssen for providing the code and working with me to get it
> > into a workable and semi-mergable state. His involvement within
> > Microsoft was also invaluable.
> > - Sam Ramji for his push within Microsoft to make this happen in a
> > manner that works with the Linux community.
> > - Novell for sponsoring my work on the Linux Driver project, without
> > which, this would not have even been possible.
> > And there are many others both within Novell and Microsoft, who I do not
> > want to slight by not naming, but the list would be too long to go into.
> >
> > These drivers are to enable Linux to work better when running as a guest
> > on top of the Hyper-V system. There is still a lot of work to do in
> > getting this into "proper" mergable state, and moving it out of the
> > staging directory, but Hank and I will be undertaking this task. See
> > the TODO file in the drivers/staging/hv/ directory if anyone wishes to
> > help out with this task.
> >
>
> What is the long term strategy to keep the sources in sync? Is there
> one? Do you expect to get updates for these sources?
The in-kernel version will be the only source for the drivers in the
long run. Eventually they will take the drivers off their web site when
the distros pick them up in their new releases.
thanks,
greg k-h
next prev parent reply other threads:[~2009-07-21 16:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-20 16:00 [patch 00/54] [Announce] Microsoft Hyper-V drivers for Linux Greg Kroah-Hartman
2009-07-20 16:28 ` Greg KH
2009-07-20 16:59 ` Dave Jones
2009-07-20 17:03 ` Greg KH
2009-07-20 17:22 ` Dave Jones
[not found] ` <871vob4047.fsf@basil.nowhere.org>
2009-07-20 19:57 ` Greg KH
2009-07-21 12:07 ` Arnd Bergmann
2009-07-21 13:38 ` Belisko Marek
2009-07-21 16:51 ` Greg KH
2009-07-20 17:09 ` Matthias Urlichs
2009-07-20 17:15 ` Dave Jones
2009-07-20 17:36 ` Greg KH
2009-07-20 21:24 ` Jan Engelhardt
2009-07-20 21:33 ` Greg KH
2009-07-21 11:06 ` Balbir Singh
2009-07-21 16:51 ` Greg KH [this message]
2009-07-21 18:00 ` Hank Janssen
2009-07-21 18:22 ` Balbir Singh
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=20090721165153.GG14746@kroah.com \
--to=greg@kroah.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=devel@driverdev.osuosl.org \
--cc=haiyangz@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shemminger@linux-foundation.org \
--cc=sramji@microsoft.com \
--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