[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <6E21E5352C11B742B20C142EB499E048081E774F@TK5EX14MBXC124.redmond.corp.microsoft.com>
Date: Sat, 17 Sep 2011 13:26:20 +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 0000/0020] Staging: hv: Driver cleanup
> -----Original Message-----
> From: Greg KH [mailto:greg@...ah.com]
> Sent: Friday, September 16, 2011 2:07 PM
> To: KY Srinivasan
> Cc: gregkh@...e.de; linux-kernel@...r.kernel.org;
> devel@...uxdriverproject.org; virtualization@...ts.osdl.org
> Subject: Re: [PATCH 0000/0020] Staging: hv: Driver cleanup
>
> On Tue, Sep 13, 2011 at 10:59:19AM -0700, K. Y. Srinivasan wrote:
> > Address Greg's VmBus audit comments:
> >
> > 1) Leverage driver_data field in struct hv_vmbus_device_id to
> > simplify driver code.
> >
> > 2) Make the util driver conform to the Linux Driver Model.
> >
> > 3) Get rid of the ext field in struct hv_device by using the
> > driver specific data functionality.
> >
> > 4) Implement vmbus specific wrapper functions for setting and getting
> > driver specific data..
> >
> > 5) Other general cleanup.
>
> I applied 17 of these (i.e. the ones I didn't comment on.)
Thanks Greg. Looking at your comments, it looks like the only
issue in the 3 patches not checked in is related to unnecessary
messages being put out. I will get the fixed patches out soon.
Regards,
K. Y
>
> greg k-h
--
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/
Powered by blists - more mailing lists