From: Kevin Hilman <khilman@deeprootsystems.com>
To: Lesly Arackal Manuel <leslyam@ti.com>
Cc: linux-omap@vger.kernel.org, 'Lesly A M' <x0080970@ti.com>,
'Nishanth Menon' <nm@ti.com>, 'David Derrick' <dderrick@ti.com>,
'Samuel Ortiz' <sameo@linux.intel.com>
Subject: Re: [PATCH v6 4/7] omap3: pm: changing vdd0_/vdd1_ to vdd1_/vdd2_ in VC param structure
Date: Fri, 04 Jun 2010 08:25:10 -0700 [thread overview]
Message-ID: <87fx12q0q1.fsf@deeprootsystems.com> (raw)
In-Reply-To: <007601cb03bb$573cef50$e08818ac@apr.dhcp.ti.com> (Lesly Arackal Manuel's message of "Fri\, 4 Jun 2010 13\:25\:46 +0530")
"Lesly Arackal Manuel" <leslyam@ti.com> writes:
> Hi Kevin,
>
>> -----Original Message-----
>> From: Kevin Hilman [mailto:khilman@deeprootsystems.com]
>> Sent: Thursday, June 03, 2010 11:15 PM
>> To: Lesly A M
>> Cc: linux-omap@vger.kernel.org; Lesly A M; Nishanth Menon; David Derrick;
>> Samuel Ortiz
>> Subject: Re: [PATCH v6 4/7] omap3: pm: changing vdd0_/vdd1_ to vdd1_/vdd2_
>> in VC param structure
>>
>> Lesly A M <leslyam@ti.com> writes:
>>
>> > Rename vdd0_/vdd1_ to vdd1_/vdd2_ in VC param structure.
>>
>> That answers "what?", but not "why?"
>>
>> Yes, I know the answer right now, but I forget things often.
>>
>> Please help ease the pain of my forgetfullness by writing a
>> descriptive changelog so when I or anyone else looks at this in the
>> git history, they will be able to understand.
>>
>> Kevin
>
> Actually there is no VDD0, its VDD1 & VDD2. So the renaming is done just to
> avoid the confusion.
Yes. As I said above, I do know why. I just want it to be in the
changelog so when I forget, it will be easy for me to remember why.
*In the changelog*, you should be stating that you are changing the
names to match the hardware documentation or something along those
lines.
Kevin
prev parent reply other threads:[~2010-06-04 15:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 12:35 [PATCH v6 4/7] omap3: pm: changing vdd0_/vdd1_ to vdd1_/vdd2_ in VC param structure Lesly A M
2010-06-03 17:44 ` Kevin Hilman
2010-06-04 7:55 ` Lesly Arackal Manuel
2010-06-04 15:25 ` Kevin Hilman [this message]
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=87fx12q0q1.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=dderrick@ti.com \
--cc=leslyam@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=sameo@linux.intel.com \
--cc=x0080970@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.