From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin Hilman Subject: Re: [PATCHV2] OMAP4: OPP: add OMAP4460 definitions Date: Wed, 20 Jul 2011 17:04:35 -0700 Message-ID: <87k4bcfqi4.fsf@ti.com> References: <1309758042-17208-1-git-send-email-vishwanath.bs@ti.com> <87wrfejo63.fsf@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from na3sys009aog114.obsmtp.com ([74.125.149.211]:55377 "EHLO na3sys009aog114.obsmtp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751906Ab1GUAEj (ORCPT ); Wed, 20 Jul 2011 20:04:39 -0400 Received: by iwi5 with SMTP id 5so641766iwi.7 for ; Wed, 20 Jul 2011 17:04:38 -0700 (PDT) In-Reply-To: (Vishwanath Sripathy's message of "Wed, 20 Jul 2011 23:00:32 +0530") Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Vishwanath Sripathy Cc: linux-omap@vger.kernel.org, paul@pwsan.com, Nishanth Menon Vishwa, Vishwanath Sripathy writes: [...] >> A quick glance now suggests it has a few minor problems. >> >> - patch was not Cc's to linux-arm-kernel >> - uses 44XX naming which is not used in l-o master > Sorry I did not get this point. What do you mean by 44XX naming? > I applied this patch against lo master and it seems to apply and compile > perfectly fine. You're right. Sorry, my fault. I thought I saw some CHIP_IS stuff in this patch using the 44XX naming that Tony did not merge for 3.1, but I was mistaken. It's only used in some register offset defines, which is fine. Kevin