public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] How to manage RMOBILE patches?
Date: Wed, 5 Sep 2012 07:17:51 -0700	[thread overview]
Message-ID: <50475F0F.8060404@ti.com> (raw)
In-Reply-To: <20120905131839.066977f2@lilith>

On 09/05/2012 04:18 AM, Albert ARIBAUD wrote:
> Hi Nobuhiro,
> 
> On Wed, 5 Sep 2012 11:26:37 +0900, Nobuhiro Iwamatsu
> <iwamatsu@nigauri.org> wrote:
> 
>> Hi,
>>
>> On Wed, Sep 5, 2012 at 2:36 AM, Tom Rini <trini@ti.com> wrote:
>>> On Mon, Sep 03, 2012 at 09:15:56PM +0200, Wolfgang Denk wrote:
>>>> Dear Nobuhiro Iwamatsu,
>>>>
>>>> In message
>>>> <CABMQnVLBEEjcEtfTzdeThHfTLp=b24QSOgnFjbZr-8YWYTJUhg@mail.gmail.com>
>>>> you wrote:
>>>>>
>>>>> I am working supporting  Renesas RMOBILE to U-Boot.
>>>>> Renesas's RMOBILE SoC family contains an ARM Cortex-A9, and this
>>>>> uses the same IP as SH.
>>>>> (For example, timer, ether, serial, etc.)
>>>>> I already sent to patches of rmobile, I got review from some
>>>>> developers. And the patch is managed by the arm/rmobile branch
>>>>> of u-boot-sh[0] which I have maintained, now.
>>>>> Since I had you take the patch of rmobile into an ARM
>>>>> repository, I consulted with Albert about the
>>>>> future development approach.
>>>>>
>>>>> We thought two methods are considered.
>>>>> One is Albert picks up a patch from ML to ARM repository,
>>>>
>>>> As this is ARM code, this appears the most natural approach to me
>>>>
>>>>> Another is whether to have pull from the repository by having a
>>>>> repository for rmobile made.
>>>>
>>>> If this is an ARM SoC, then it should go through the ARM repo -
>>>> even if we should later decide that there is so much traffic that a
>>>> separate rmobile repo would be sustified, thi would still be a
>>>> sub-repo, which Albert would pull from.
>>>
>>> Another option, which Mike is using for, iirc, sf and blackfin, is
>>> just to add rmobile-master / rmobile-next as branches to the
>>> u-boot-sh repository.
>>
>> Yes, this is one of easy way. But Albert won't  pull form u-boot-sh,
>> if If my understanding is not wrong.
> 
> This just means that they'll end up on u-boot/master from u-boot.sh (and
> from there into u-boot-arm later on).

To be clear, what I'm saying is just add a few more branches to
u-boot-sh that Albert will pull (since they're ARM stuff).  Say
u-boot-sh/rmobile/master and u-boot-sh/rmobile/next.  Then not get too
hung up on which repository a merge message comes from. :)

-- 
Tom

  reply	other threads:[~2012-09-05 14:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-03  0:46 [U-Boot] How to manage RMOBILE patches? Nobuhiro Iwamatsu
2012-09-03 19:15 ` Wolfgang Denk
2012-09-04 17:36   ` Tom Rini
2012-09-05  2:26     ` Nobuhiro Iwamatsu
2012-09-05 11:18       ` Albert ARIBAUD
2012-09-05 14:17         ` Tom Rini [this message]
2012-09-05 23:20           ` Nobuhiro Iwamatsu
2012-09-06 19:28             ` Albert ARIBAUD
2012-09-06 20:58               ` Tom Rini
2012-09-07 17:09                 ` Albert ARIBAUD
2012-09-10  0:41                   ` Nobuhiro Iwamatsu
2012-09-23 22:48                     ` Nobuhiro Iwamatsu
2012-09-10  0:37               ` Nobuhiro Iwamatsu
2012-09-05  2:22   ` Nobuhiro Iwamatsu

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=50475F0F.8060404@ti.com \
    --to=trini@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