-----Original Message----- > From: linux-omap-owner@xxxxxxxxxxxxxxx > [mailto:linux-omap-owner@xxxxxxxxxxxxxxx] On Behalf Of > Shilimkar, Santosh > Sent: Tuesday, April 21, 2009 7:05 PM > To: Premi, Sanjeev; linux-omap@xxxxxxxxxxxxxxx > Subject: RE: [PATCH 4/7][RFC] OMAP4: Update common omap > platform common sources. > > > -----Original Message----- > > From: Premi, Sanjeev > > Sent: Tuesday, April 21, 2009 6:51 PM > > To: Shilimkar, Santosh; linux-omap@xxxxxxxxxxxxxxx > > Cc: Shilimkar, Santosh > > Subject: RE: [PATCH 4/7][RFC] OMAP4: Update common omap > > platform common sources. > > > > Any specific reason to use omap2 structures? > > These are not actually the omap2 structures. Most of the > common omap code uses something like > 'omap2_xxxxx_xxx'. Not sure but may be mostly because of the common feautres beteen OMAP2, OMAP3 and now OMAp4 as well. cpu_class_omap2() ==> omap2/omap3/omap4.-- 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
