linux-kernel - RE: [PATCH 00/16] Staging: hv: Consolidate driver and device abstractions

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] [day] [month] [year] [list]

Message-ID: <6E21E5352C11B742B20C142EB499E048017443@TK5EX14MBXC128.redmond.corp.microsoft.com>
Date:	Mon, 7 Mar 2011 23:17:19 +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: [PATCH 00/16] Staging: hv: Consolidate driver and device
 abstractions



> -----Original Message-----
> From: Greg KH [mailto:greg@...ah.com]
> Sent: Monday, March 07, 2011 6:00 PM
> To: KY Srinivasan
> Cc: gregkh@...e.de; linux-kernel@...r.kernel.org;
> devel@...uxdriverproject.org; virtualization@...ts.osdl.org
> Subject: Re: [PATCH 00/16] Staging: hv: Consolidate driver and device
> abstractions
> 
> On Mon, Mar 07, 2011 at 10:45:15PM +0000, KY Srinivasan wrote:
> > > I'm guessing that you will have follow-on patches now to complete the
> > > migration to the correct driver core use (i.e. proper driver and device
> > > usage?)  Or do you want me to look into doing this?
> >
> > My immediate goal is to get the vmbus driver to exit staging. To that
> > end I am working on a patch-set to cleanup vmbus_drv.c. I should have this
> > patch-set fairly soon.  Once that is
> > done, I think we would have addressed all the structural/architectural issues
> > of the vmbus driver that is preventing us from exiting staging.
> 
> Well, perhaps, let's not get ahead of ourselves here :)

Certainly. I was being presumptuous when I said  "we would have
addressed all the structural/architectural issues ..".  What I meant 
to say was that I would have addressed  the problems that I know about.
After I am done with the current cleanup, I will work on the remaining 
issues.

> 
> > We are planning to address the issues with other drivers after we are done
> > with the vmbus driver. As always, your help is greatly appreciated.
> 
> The issue I am referring to above still has to do with the vmbus core.
> 
> The goal is to have the vmbus work like all other busses in the kernel.
> You register a hv_driver with some probe and disconnect callbacks, and
> the vmbus calls into the drivers when it needs to.
> 
> You are almost there, using the struct device pointers directly, but a
> few more steps remain.
> 
> I'll look into the details after your remaining cleanups, I don't want
> to get in the way of them.

Thank you. You should have my patches fairly soon. Hopefully, I would 
have addressed the issues you have raised.  

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/