From: Albert ARIBAUD <albert.aribaud@free.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARM: Update mach-types
Date: Thu, 17 Feb 2011 23:40:23 +0100 [thread overview]
Message-ID: <4D5DA3D7.6030908@free.fr> (raw)
In-Reply-To: <0554BEF07D437848AF01B9C9B5F0BC5DC192BF29@dlee01.ent.ti.com>
Le 17/02/2011 23:28, Paulraj, Sandeep a ?crit :
>
>
>>>
>>>
>>>>
>>>> Hi Sandeep,
>>>>
>>>> Le 16/02/2011 22:15, s-paulraj at ti.com a ?crit :
>>>>> From: Sandeep Paulraj<s-paulraj@ti.com>
>>>>>
>>>>> This commit updates the mach-types based on the latest
>>>>> in linus's head
>>>>
>>>> Aaaaah, telepathy at last! :)
>>>>
>>>>> -#define MACH_TYPE_SUEN3 2255
>>>>> +#define MACH_TYPE_KM_KIRKWOOD 2255
>>>>
>>>>> -#define MACH_TYPE_TEGRA_SEABOARD 3005
>>>>> +#define MACH_TYPE_SEABOARD 3005
>>>>
>>>>> -#define MACH_TYPE_SBC_NT250 3209
>>>>> +#define MACH_TYPE_TRIMSLICE 3209
>>>>
>>>> I don't follow the Linux tree closely. Are these renames normal?
>>>
>>> Yes absolutely normal.
>>> WE have done this several times in U-Boot
>>
>> Fine, then. :)
>>
>>>> Won't
>>>> that break something for us?
>>>
>>> Even if it does, The name change occurred because the appropriate
>> maintainer changed it. The change will have to be made in U-boot if
>> required.
>>
>> All right. I'll add this in u-boot-arm/next later today, with a Cc: to
>> board maintainers of the three renamed machines.
>>
> This is reasonably important. Why can't it goto master
Because the merge window is closed and thus, only patches that were
submitted initially before closure, or bug fixes, can go into master
right now.
> Regards,
> Sandeep
Amicalement,
--
Albert.
next prev parent reply other threads:[~2011-02-17 22:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 21:15 [U-Boot] [PATCH] ARM: Update mach-types s-paulraj at ti.com
2011-02-17 11:55 ` Albert ARIBAUD
2011-02-17 16:27 ` Paulraj, Sandeep
2011-02-17 17:32 ` Albert ARIBAUD
2011-02-17 22:28 ` Paulraj, Sandeep
2011-02-17 22:40 ` Albert ARIBAUD [this message]
2011-02-17 22:47 ` Wolfgang Denk
2011-02-17 23:00 ` Albert ARIBAUD
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=4D5DA3D7.6030908@free.fr \
--to=albert.aribaud@free.fr \
--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