From mboxrd@z Thu Jan 1 00:00:00 1970 From: Omar Ramirez Luna Subject: [UPDATE] kill camel case Date: Mon, 1 Mar 2010 21:07:01 -0600 Message-ID: <4B8C80D5.6020803@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from devils.ext.ti.com ([198.47.26.153]:59597 "EHLO devils.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751472Ab0CBDHF (ORCPT ); Mon, 1 Mar 2010 22:07:05 -0500 Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: "linux-omap@vger.kernel.org" Cc: Tony Lindgren , "Menon, Nishanth" , "Ameya.Palande@nokia.com" , Felipe Contreras Hi All, CamelCase script execution has been completed, so far I replaced all the tokens picked up by the killcc script[1], and all the changes are present in the following branches: dspbridge-next-camelcase ------------------------ It has all the changes made in three steps: 1) Replaced all the new tokens not present in bridge code, after that solved compilation problems caused by symbols with same name as kernel symbols. 2) Replaced tokens that were already present in bridge code either as symbols or strings. 3) Replaced tokens generated by script, which were same as other symbols, i.e. hChnlMgr and pChnlMgr will generate chnl_mgr. dspbridge-next-camelcase2 ------------------------- It has the same changes as above but these are broken into single patches. Total number of patches: 2795 diff-stat: 157 files changed, 18385 insertions(+), 18385 deletions(-) Please take a look to the logs[2] as they might be easier to review rather than looking at each patch. Also I placed the steps to follow on the patch commits of dspbridge-next-camelcase. - omar --- [1] http://marc.info/?l=linux-omap&m=125353475429517&w=2 [2] https://gforge.ti.com/gf/project/omapbridge/docman/?subdir=30, logs for point 2 and 3 have the following format for tokens | |