On Fri, Jan 15, 2010 at 03:38:15AM +0100, G?bor Stefanik wrote: > On Fri, Jan 15, 2010 at 3:31 AM, Greg KH <greg@xxxxxxxxx> wrote: > > On Fri, Jan 15, 2010 at 02:41:42AM +0100, G?bor Stefanik wrote: > >> On Fri, Jan 15, 2010 at 1:55 AM, Greg KH <greg@xxxxxxxxx> wrote: > >> > On Wed, Jan 06, 2010 at 05:07:21PM +0800, Wu Zhangjin wrote: > >> >> Hi, Greg K-H > >> >> > >> >> Sorry to disturb you, Teddy just sent a bug fix to me after I sending > >> >> this patch out, I will test the bugfix, if it works, will send it out > >> >> instead of this patch. > >> > > >> > What happened with this? ?Did your bugfix work out? > >> > > >> > Should I apply this or not? > >> > >> BTW this is exactly what the &&BROKEN label is for. > > > > No, I delete drivers in staging that are broken. > > > > thanks, > > > > greg k-h > > > > But here it's not a whole driver that is broken, just a specific > feature, which is what BROKEN represents. That's why I will be glad to take the "delete this code" patch, if this is the correct thing. Again, I don't want to use BROKEN in staging drivers. thanks, greg k-h _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
