From: Omar Ramirez Luna <omar.ramirez@ti.com>
To: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Cc: Tony Lindgren <tony@atomide.com>, "Menon, Nishanth" <nm@ti.com>,
"Ameya.Palande@nokia.com" <Ameya.Palande@nokia.com>,
Felipe Contreras <felipe.contreras@nokia.com>
Subject: [UPDATE] kill camel case
Date: Mon, 1 Mar 2010 21:07:01 -0600 [thread overview]
Message-ID: <4B8C80D5.6020803@ti.com> (raw)
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 <old> | <new> |
<comments>
next reply other threads:[~2010-03-02 3:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-02 3:07 Omar Ramirez Luna [this message]
2010-03-08 17:58 ` [UPDATE] kill camel case Omar Ramirez Luna
2010-03-08 18:10 ` Deepak Chitriki
2010-03-08 18:33 ` Omar Ramirez Luna
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B8C80D5.6020803@ti.com \
--to=omar.ramirez@ti.com \
--cc=Ameya.Palande@nokia.com \
--cc=felipe.contreras@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=tony@atomide.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox