All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sricharan R <r.sricharan@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V3 1/3] OMAP5: I2C: Enable i2c5 clocks
Date: Tue, 9 Apr 2013 12:12:20 +0530	[thread overview]
Message-ID: <5163B84C.5030308@ti.com> (raw)
In-Reply-To: <5163B7B9.5060708@mm-sol.com>

On Tuesday 09 April 2013 12:09 PM, Lubomir Popov wrote:
> Hi Sricharan,
> 
> On 09/04/13 09:34, Sricharan R wrote:
>> Hi Lubomir,
>>
>> On Monday 08 April 2013 04:03 PM, Lubomir Popov wrote:
>>> Signed-off-by: Lubomir Popov <lpopov@mm-sol.com>
>>> ---
>>> V3 consolidates this patch into a series.
>>>
>>>  arch/arm/cpu/armv7/omap5/hw_data.c |    1 +
>>>  1 file changed, 1 insertion(+)
>>>
>>> diff --git a/arch/arm/cpu/armv7/omap5/hw_data.c b/arch/arm/cpu/armv7/omap5/hw_data.c
>>> index e5e41fd..5698876 100644
>>> --- a/arch/arm/cpu/armv7/omap5/hw_data.c
>>> +++ b/arch/arm/cpu/armv7/omap5/hw_data.c
>>> @@ -412,6 +412,7 @@ void enable_basic_uboot_clocks(void)
>>>  		(*prcm)->cm_l4per_i2c2_clkctrl,
>>>  		(*prcm)->cm_l4per_i2c3_clkctrl,
>>>  		(*prcm)->cm_l4per_i2c4_clkctrl,
>>> +		(*prcm)->cm_l4per_i2c5_clkctrl,
>>>  		(*prcm)->cm_l3init_hsusbhost_clkctrl,
>>>  		(*prcm)->cm_l3init_fsusb_clkctrl,
>>>  		0
>>
>>   Please note that whatever is above the '----' gets committed.
>>   So now all the 3 patches will not have any commit message.
> 
> Ooops... So much work, so little time... Should I do a V4?
> 

ya, because a patch without a commit log would look really blank :)

Regards,
 Sricharan

      reply	other threads:[~2013-04-09  6:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-08 10:33 [U-Boot] [PATCH V3 1/3] OMAP5: I2C: Enable i2c5 clocks Lubomir Popov
2013-04-09  6:34 ` Sricharan R
2013-04-09  6:39   ` Lubomir Popov
2013-04-09  6:42     ` Sricharan R [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=5163B84C.5030308@ti.com \
    --to=r.sricharan@ti.com \
    --cc=u-boot@lists.denx.de \
    /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.