> -----Original Message----- > From: Premi, Sanjeev [mailto:premi@xxxxxx] > Sent: Thursday, January 06, 2011 7:26 PM > To: Shilimkar, Santosh; linux-omap Mailing List > Subject: RE: Errors when building for omap4 only > > > > > -----Original Message----- > > From: Shilimkar, Santosh > > Sent: Thursday, January 06, 2011 7:19 PM > > To: Premi, Sanjeev; linux-omap Mailing List > > Subject: RE: Errors when building for omap4 only > > > > Sanjeev, > > > -----Original Message----- > > > From: linux-omap-owner@xxxxxxxxxxxxxxx [mailto:linux-omap- > > > owner@xxxxxxxxxxxxxxx] On Behalf Of Premi, Sanjeev > > > Sent: Thursday, January 06, 2011 6:18 PM > > > To: linux-omap Mailing List > > > Subject: Errors when building for omap4 only > > > > > > Hi all, > > > > > > I was trying to build OMAP4 only kernel from the linux-omap > master. > > > Came across few failures caused by exclusion of OMAP3/3 specific > > > code via #ifdef. > > > > > These are addressed already. You could look at below series > > http://www.mail-archive.com/linux- > omap@xxxxxxxxxxxxxxx/msg41712.html > > > > Great! I missed the series. > > Question (after quick browse): Don't addition stubs add too many > strings to the code? > They do. But we want these functions to throw warning when they are used on wrong SOCS. So that wrong usage is avoided and if exist can be killed. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
