From: Sricharan R <r.sricharan@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V4 5/5] ARM: OMAP4/5: Make bootz as the default boot command
Date: Fri, 5 Apr 2013 13:58:05 +0530 [thread overview]
Message-ID: <515E8B15.6070601@ti.com> (raw)
In-Reply-To: <20130405100826.685f4dce@lilith>
On Friday 05 April 2013 01:38 PM, Albert ARIBAUD wrote:
> Hi Sricharan,
>
> On Fri, 5 Apr 2013 12:44:45 +0530, Sricharan R <r.sricharan@ti.com>
> wrote:
>
>> Hi Albert,
>>
>> On Friday 05 April 2013 12:36 PM, Albert ARIBAUD wrote:
>>> Hi Sricharan,
>>>
>>> On Fri, 5 Apr 2013 11:24:34 +0530, Sricharan R <r.sricharan@ti.com>
>>> wrote:
>>>
>>>> So with OMAP added to multi platform kernel,
>>>> the uImage no more contains a valid load address.
>>>> With the uboot already supporting zImage,
>>>> change the default boot command to bootz
>>>> instead.
>>>>
>>>> Acked-by: Nishanth Menon <nm@ti.com>
>>>> Signed-off-by: Sricharan R <r.sricharan@ti.com>
>>>> Tested-by: Nishanth Menon <nm@ti.com>
>>>> ---
>>>> include/configs/omap4_common.h | 4 ++--
>>>> include/configs/omap5_common.h | 4 ++--
>>>> 2 files changed, 4 insertions(+), 4 deletions(-)
>>>
>>> Is there a reason why this patch does not have history?
>>>
>>> Amicalement,
>> I had a minor change only in these two from the series.
>> So reposted only these two with 'in-reply-to' threads.
>> If this is not the right etiquette, then should it be
>> update/appended in the original patch ?
>
> My question is not about the series but only about 5/5 which has
> no patch history after the commit message delimiter (---) whereas 4/5
> has history.
>
> If 5/5 has a minor change in V4, then it should have a history log
> indicating which minor change it was.
>
ok. 5/5 was just rebase on 4/5. Will add it though.
Sorry for the miss.
Regards,
Sricharan
next prev parent reply other threads:[~2013-04-05 8:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-01 15:52 [U-Boot] [PATCH V4 0/5] ARM: OMAP4/5: Add support to boot with device tree as default Sricharan R
2013-04-01 15:52 ` [U-Boot] [PATCH V4 1/5] ARM: OMAP5: Rename omap5_evm to omap5_uevm Sricharan R
2013-04-01 15:52 ` [U-Boot] [PATCH V4 2/5] ARM: OMAP5: Set fdt_high to enable booting with Device tree Sricharan R
2013-04-01 15:52 ` [U-Boot] [PATCH V4 3/5] omap5: Allow use of a plain text env file Sricharan R
2013-04-01 15:52 ` [U-Boot] [PATCH V4 4/5] ARM: OMAP4/5: Change the default boot command to work with device tree Sricharan R
2013-04-01 19:20 ` Tom Rini
2013-04-02 15:33 ` Sricharan R
2013-04-02 16:13 ` Tom Rini
2013-04-02 17:07 ` Sricharan R
2013-04-05 5:54 ` Sricharan R
2013-04-05 5:54 ` [U-Boot] [PATCH V4 5/5] ARM: OMAP4/5: Make bootz as the default boot command Sricharan R
2013-04-05 7:06 ` Albert ARIBAUD
2013-04-05 7:14 ` Sricharan R
2013-04-05 8:08 ` Albert ARIBAUD
2013-04-05 8:28 ` Sricharan R [this message]
2013-04-05 9:39 ` [U-Boot] [PATCH V4 4/5] ARM: OMAP4/5: Change the default boot command to work with device tree Sricharan R
2013-04-05 9:39 ` [U-Boot] [PATCH V4 5/5] ARM: OMAP4/5: Make bootz as the default boot command Sricharan R
2013-04-01 15:52 ` Sricharan R
2013-04-08 16:58 ` [U-Boot] [PATCH V4 0/5] ARM: OMAP4/5: Add support to boot with device tree as default Tom Rini
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=515E8B15.6070601@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox