public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom <Tom.Rix@windriver.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-boot] Marvell Pull Request
Date: Tue, 22 Sep 2009 08:20:11 -0500	[thread overview]
Message-ID: <4AB8CF0B.5070404@windriver.com> (raw)
In-Reply-To: <73173D32E9439E4ABB5151606C3E19E202ED512D36@SC-VEXCH1.marvell.com>

Prafulla Wadaskar wrote:
>  
> 
>> -----Original Message-----
>> From: Tom [mailto:Tom.Rix at windriver.com] 
>> Sent: Tuesday, September 22, 2009 12:46 AM
>> To: Prafulla Wadaskar
>> Cc: U-Boot
>> Subject: Re: [U-Boot] [U-boot] Marvell Pull Request
>>
>> Prafulla Wadaskar wrote:
>>> Hi Wolfgang
>>>
>>> Please pull
>> Shouldn't this rather get pulled to u-boot-arm?
>> Tom
> 
> Hi Tom,
> Yes :-) you are right.
> I was bit biased since u-boot-marvell.git was cloned from u-boot.git
> Shall I generate new email pull request? Or
> Can you please kindly pull it to u-boot-arm?

I would like to set up a process where I just cherry picked your changes
directly from marvell/master.

Comparing marvell/master to arm/next

git cherry t-next
+ ceb2d57c2205db5bbd868577f756c74a2568160c
+ 95a4a593b577b6e2f1da2d4b0f5ec86975c33413
+ 84a45d33c2cc261dbd5411f7c2ad45f6003025b6
+ e67af44d0167d8237dd2c2ddf8e301d19ca12914
+ 0413cfecea350000eab5e591a0965c3e3ee0ff00
+ 3b6a9267f0de7b85d387fa4123d0b58379363447
+ ffed6c85ce591cd93e28190153fec421c3b2499c <- pick me
+ c928c19b2563e4977adc0570d06c900ac1e7788c <- pick me
+ 9ef0569a3c8b0d2458bdbce21a5370807e13e20a <- pick me

The others look like they came from u-boot/master

It would be helpful but not required if you merged against arm/master or 
arm/next instead of u-boot/master.

If I can assume what is good in marvell/master, we do not need
for you go through the asking for a pulls, they will just happen
when I have time, likely over the weekend.

These changes will accumulate in arm/next.
Less frequently I will merge these to arm/master.
This will happen once you and the other arm maintainers have
given then the ok.  I was thinking that this could happen monthly
but I am open for other suggestions.

Tom

> 
> Regards..
> Prafulla . .
> 
>>
>>> The following changes since commit 
>> 3b6a9267f0de7b85d387fa4123d0b58379363447:
>>>   Wolfgang Denk (1):
>>>         board/flagadm/flash.c: fix compile warning
>>>
>>> are available in the git repository at:
>>>
>>>   git://git.denx.de/u-boot-marvell.git master
>>>
>>> Prafulla Wadaskar (2):
>>>       Kirkwood: rd6281a: Add kwbimage build support
>>>       Kirkwood: mv88f6281gtw_ge: Add kwbimage build support
>>>
>>> Simon Kagstrom (1):
>>>       Support for the OpenRD base board
>>>
>>>  MAINTAINERS                                |    4 +
>>>  MAKEALL                                    |    1 +
>>>  Makefile                                   |    3 +
>>>  board/Marvell/mv88f6281gtw_ge/config.mk    |    3 +
>>>  board/Marvell/mv88f6281gtw_ge/kwbimage.cfg |  165 
>> +++++++++++++++++++++
>>>  board/Marvell/openrd_base/Makefile         |   56 +++++++
>>>  board/Marvell/openrd_base/config.mk        |   33 ++++
>>>  board/Marvell/openrd_base/kwbimage.cfg     |  168 
>> +++++++++++++++++++++
>>>  board/Marvell/openrd_base/openrd_base.c    |  160 
>> ++++++++++++++++++++
>>>  board/Marvell/openrd_base/openrd_base.h    |   46 ++++++
>>>  board/Marvell/rd6281a/config.mk            |    3 +
>>>  board/Marvell/rd6281a/kwbimage.cfg         |  167 
>> +++++++++++++++++++++
>>>  include/configs/openrd_base.h              |  220 
>> ++++++++++++++++++++++++++++
>>>  13 files changed, 1029 insertions(+), 0 deletions(-)
>>>  create mode 100644 board/Marvell/mv88f6281gtw_ge/kwbimage.cfg
>>>  create mode 100644 board/Marvell/openrd_base/Makefile
>>>  create mode 100644 board/Marvell/openrd_base/config.mk
>>>  create mode 100644 board/Marvell/openrd_base/kwbimage.cfg
>>>  create mode 100644 board/Marvell/openrd_base/openrd_base.c
>>>  create mode 100644 board/Marvell/openrd_base/openrd_base.h
>>>  create mode 100644 board/Marvell/rd6281a/kwbimage.cfg
>>>  create mode 100644 include/configs/openrd_base.h
>>>
>>> Regards..
>>> Prafulla . . .
>>> _______________________________________________
>>> U-Boot mailing list
>>> U-Boot at lists.denx.de
>>> http://lists.denx.de/mailman/listinfo/u-boot

  reply	other threads:[~2009-09-22 13:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-21 17:14 [U-Boot] [U-boot] Marvell Pull Request Prafulla Wadaskar
2009-09-21 19:15 ` Tom
2009-09-22  9:28   ` Prafulla Wadaskar
2009-09-22 13:20     ` Tom [this message]
2009-09-23  6:13       ` Prafulla Wadaskar
2009-09-23 11:23         ` Tom
2009-09-23 22:12       ` Wolfgang Denk
2009-09-24  1:07         ` Tom
2009-09-24 10:11           ` Wolfgang Denk
2009-09-24 10:23             ` Tom
2009-09-27 23:51     ` Tom
2009-09-29  1:21       ` Prafulla Wadaskar

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=4AB8CF0B.5070404@windriver.com \
    --to=tom.rix@windriver.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