public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: "Menon, Nishanth" <nm@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: "Ramirez Luna, Omar" <omar.ramirez@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [ANNOUNCE] dspbridge: kill camelcase
Date: Wed, 24 Feb 2010 09:38:01 +0200	[thread overview]
Message-ID: <4B84D759.7000801@ti.com> (raw)
In-Reply-To: <20100224031325.GM28173@atomide.com>

Tony Lindgren said the following on 02/24/2010 05:13 AM:
> * Omar Ramirez Luna <omar.ramirez@ti.com> [100223 18:11]:
>> Hi All,
>>
>> I'm currently working on removing camel case + hungarian notation
>> from dspbridge code in the following branch:
>>
>> dspbridge-next-camelcase on d.o-z
>>
>> I'll appreciate if you can mail any unsent patch otherwise it will
>> need to wait (and be rebased) after the camelcase changes.
>>
>> If nobody disagrees I'll be marking dspbridge 0.2 (as per private
>> discussion) in the upcoming days.
> 
> Maybe do a perl or sed script that allows you to convert one
> string at a time? That way you can regenerate the patches as
> needed.
> 
> We used something like that to convert the musb code a few
> years ago.
> 
> I recommend converting one variable at a time and then compile
> and boot test in between. Otherwise you can easily convert
> substrings accidentally and then things will not compile..

I think we discussed this quiet some time back:
http://marc.info/?t=125319739500001&r=1&w=2 - yep there is script 
available.

-- 
Regards,
Nishanth Menon

  reply	other threads:[~2010-02-24  7:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-24  2:14 [ANNOUNCE] dspbridge: kill camelcase Omar Ramirez Luna
2010-02-24  3:13 ` Tony Lindgren
2010-02-24  7:38   ` Menon, Nishanth [this message]
2010-02-24 17:02     ` 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=4B84D759.7000801@ti.com \
    --to=nm@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=omar.ramirez@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