linux-kernel - RE: vmbus driver

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:	Fri, 20 May 2011 13:21:36 +0000
From:	KY Srinivasan <kys@...rosoft.com>
To:	Greg KH <greg@...ah.com>
CC:	"gregkh@...e.de" <gregkh@...e.de>,
	"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: vmbus driver



> -----Original Message-----
> From: Greg KH [mailto:greg@...ah.com]
> Sent: Friday, May 20, 2011 9:05 AM
> To: KY Srinivasan
> Cc: gregkh@...e.de; linux-kernel@...r.kernel.org;
> devel@...uxdriverproject.org; virtualization@...ts.osdl.org
> Subject: Re: vmbus driver
> 
> On Thu, May 19, 2011 at 03:06:25PM -0700, K. Y. Srinivasan wrote:
> >
> > Greg,
> >
> > A few days ago you applied all the outstanding patches for the Hyper-V
> > drivers. With these patches, I have addressed all of the known review
> > comments for the  vmbus driver (and a lot of comments/issues in other
> > drivers as well). I am still hoping I can address
> > whatever other issues/comments there might be with the intention to
> > get the vmbus driver out of staging in the current window. What is your
> > sense in terms of how feasible this is. From my side, I can assure you
> > that I will address all legitimate issues in a very timely manner and this
> > will not be dependent upon the location of the drivers (staging or
> > outside staging). Looking forward to hearing from you.
> 
> The merge window is closed now, and I'm on the road in asia for about 3
> weeks, so doing this, at this point in the development cycle, is going
> to be hard.
> 
> I'll go review the bus code again after the code is all merged with
> Linus, which should take a week or so depending on my schedule, and let
> you know what's left to do (I think there still is something wierd with
> the way the hv_driver is structured, but I could be wrong.)

Thanks Greg. I look forward to your feedback.

> 
> In the mean time, I'm sure the block and network driver still need a lot
> of work, and merging the bus code doesn't make much sense without them
> as a user as that is what people really want to use, so you can continue
> to work on them.

I will continue to cleanup the block and network driver code. As you know the
util driver is also a client of the vmbus driver (as far as the communication with 
the host goes). So, it may still make sense to plan for getting the vmbus driver out 
of staging along with the util and the timesource driver. 

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/