[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 12 Dec 2011 23:50:44 +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>,
"ohering@...e.com" <ohering@...e.com>
Subject: RE: [PATCH 0000/0004] Drivers: hv: Fixes
> -----Original Message-----
> From: Greg KH [mailto:greg@...ah.com]
> Sent: Monday, December 12, 2011 5:28 PM
> To: KY Srinivasan
> Cc: gregkh@...e.de; linux-kernel@...r.kernel.org;
> devel@...uxdriverproject.org; virtualization@...ts.osdl.org; ohering@...e.com
> Subject: Re: [PATCH 0000/0004] Drivers: hv: Fixes
>
> On Mon, Dec 12, 2011 at 09:28:51AM -0800, K. Y. Srinivasan wrote:
> > Some fixes to the vmbus driver:
> >
> > 1. Fix a memory leak in a failure path.
> >
> > 2. Make vmbus driver unloadable.
> >
> > 3. Get rid of an unnecessary check in hv_init()
> > in preparation for supporting kexec().
> >
> > 4. Make it possible to build the vmbus driver as part of the
> > kernel. This patch was submitted earlier, but seems to have been
> > lost.
>
> No, it was not lost, it was applied to my driver-core-next tree a while
> ago. Because of this, I had to hand-edit patch 2 above and skip patch 4
> here.
Thanks Greg. I will check to see why I got some stale bits yesterday.
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/
Powered by blists - more mailing lists