Hi,
Deleted: dspbridge-next-camelcase
Published dspbridge-camelcase-v2
Following patches were dropped:
dspbridge: camelcase replace DSP_FAILED for dsp_failed
dspbridge: camelcase replace GB_NOBITS for gb_nobits
dspbridge: camelcase replace BITS_PER_BYTE for bits_per_byte
dspbridge: camelcase replace CINIT_PAGE_BITS for cinit_page_bits
dspbridge: camelcase replace DSPBRIDGE_VERSION for dspbridge_version
dspbridge: camelcase replace LOG_BITS_PER_BYTE for log_bits_per_byte
dspbridge: camelcase replace MMU_GFLUSH for mmu_gflush
dspbridge: camelcase replace SCALE_BITS for scale_bits
dspbridge: camelcase replace TGTAU_BITS for tgtau_bits
Modified
dspbridge: camelcase replace MAP_L4PERIPHERAL for map_l4_peripheral
renamed map_l4peripheral ==> map_l4_peripheral
dspbridge: camelcase replace MemInfo for mem_seg_info
renamed mem_seg__info ==> mem_seg_info
String replacements were fixed (i.e. replacementes made for Write,
Allocate, Deallocate)
Compilation break if compiled as part of the kernel on msg_init.
If no more comments I'll push this as a single patch after 0.2.
Regards,
Omar
On 3/1/2010 9:07 PM, Omar Ramirez Luna wrote:
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>
--
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
