linux-kernel - RE: Hyper-V TODO file

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 4 Oct 2011 17:23:51 +0000
From:	KY Srinivasan <kys@...rosoft.com>
To:	Greg KH <gregkh@...e.de>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"devel@...uxdriverproject.org" <devel@...uxdriverproject.org>,
	"virtualization@...ts.osdl.org" <virtualization@...ts.osdl.org>
Subject: RE: Hyper-V TODO file



> -----Original Message-----
> From: Greg KH [mailto:gregkh@...e.de]
> Sent: Tuesday, October 04, 2011 1:04 PM
> To: KY Srinivasan
> Cc: linux-kernel@...r.kernel.org; devel@...uxdriverproject.org;
> virtualization@...ts.osdl.org
> Subject: Re: Hyper-V TODO file
> 
> On Tue, Oct 04, 2011 at 01:59:56PM +0000, KY Srinivasan wrote:
> > Greg, sometime back you checked in the changes to the TODO file reflecting
> > that there are no outstanding vmbus related issues. What is the process now
> > for getting the vmbus (and util) drivers out of staging. Let me know if there is
> > something I can do to help this along.  As you know, we had posted the
> network
> > driver for public review a while ago (several months ago) and we have
> addressed
> > all the review comments we got. Any guidance on what we should do next
> would be
> > greatly appreciated.
> 
> At this point in time, just ask me, and I will move the files.
> 
> So, to confirm, you want to have the following files moved to
> drivers/hv/:
> 	drivers/staging/hv/Kconfig (part of this file)
> 	drivers/staging/hv/Makefile (part of this file)
> 	drivers/staging/hv/vmbus_drv.c
> 	drivers/staging/hv/hv.c
> 	drivers/staging/hv/connection.c
> 	drivers/staging/hv/channel.c
> 	drivers/staging/hv/channel_mgmt.c
> 	drivers/staging/hv/ring_buffer.c
> 	drivers/staging/hv/hv_util.c
> 	drivers/staging/hv/hv_kmp.c
This is hv_kvp.c
> 	drivers/staging/hv/hv_kvp.h
> 	drivers/staging/hv/hyperv_vmbus.h
> 

Yes; this would be the list of files to be moved to drivers/hv/

> The following file moved to include/linux/:
> 	drivers/staging/hv/hyperv.h
> (I think there is stuff in there that can go into hyperv_vmbus.h as it's
> not needed in the "global" directory, but I can do that movement.)
> 

Correct.
> The following file moved to tools/hv/:
> 	drivers/staging/hv/tools/*
> 
> And the following files modified to tie drivers/hv/ into the build service:
> 	drivers/Makefile
> 	drivers/Kconfig
> 
> Is all of that correct?
> 

Yes; the list you have is correct. Thanks a lot for doing this.

Regards,

K. Y

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/