staging/dt3155: fix build error caused by {write|read}l change
in [Kernel]
|
Prev: IIO: Fix adding more than one iio device eventset
Next: staging: frontier: fix extra spaces in tranzport.c
From: Greg KH on 8 Apr 2010 16:30 On Wed, Mar 03, 2010 at 11:24:06AM -0700, H Hartley Sweeten wrote: > This fixes a build error caused by replacing {Write | Read}MReg with > {write | read}l. Ick, can you merge this with your other patch so we don't have build errors? I just hit this and I had to drop all of your patches. Can you respin all of them please? thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Greg KH on 8 Apr 2010 16:50
On Thu, Apr 08, 2010 at 03:38:06PM -0500, H Hartley Sweeten wrote: > On Thursday, April 08, 2010 12:11 PM, Greg KH wrote: > > On Wed, Mar 03, 2010 at 11:24:06AM -0700, H Hartley Sweeten wrote: > >> This fixes a build error caused by replacing {Write | Read}MReg with > >> {write | read}l. > > > > Ick, can you merge this with your other patch so we don't have build > > errors? I just hit this and I had to drop all of your patches. > > I was expecting you to NAK all of them anyway after I saw all the code > cleanup patches coming in on LKML. > > > Can you respin all of them please? > > Not a problem. Are you planning on merging any of the dt3155 cleanup > patches? If so I will wait until they show up. I took some, you should have gotten the responses now. > Also, should staging patches be based on linux-next or on Linus' git tree? linux-next please. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |