From: Abdoulaye Walsimou Gaye <walsimou@walsimou.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] ARM pull request v3
Date: Tue, 13 Oct 2009 15:34:28 +0200 [thread overview]
Message-ID: <4AD481E4.9050200@walsimou.com> (raw)
In-Reply-To: <4AD478AE.10302@bumblecow.com>
Tom Rix a ?crit :
> Wolfgang,
>
> I have cleaned up the commits to arm/master-sync.
>
> The cleanup is from doing a
> git rev-list --reverse master..arm/master
> Then working back from my notes to take only the commits
> were either misc arm or other arm pull requests.
> These were cherry picked on top of the current u-boot/master.
>
> I ran the MAKEALL regression and the results look like
> what I posted on Sunday.
>
> That said, it would be a good idea to wait a bit for others to
> review this list and pick up on anything that I missed.
>
> I will be offline for about 10hrs and will fix any problems
> then.
>
> Tom
>
> The following changes since commit 14abfe361b3ed23b02f564e2f5d663e158cd5799:
> Wolfgang Denk (1):
> Merge branch 'master' of /home/wd/git/u-boot/custodians
>
> are available in the git repository at:
>
> git://git.denx.de/u-boot-arm master-sync
>
> Daniel Gorsulowski (1):
> at91: Update MEESC board support
>
> Dirk Behme (1):
> OMAP3 MMC: Fix warning dereferencing type-punned pointer
>
> Olof Johansson (3):
> OMAP3: Clean up whitespace in mux configs
> SMC911X: Add chip auto detection
> TI: OMAP3: Overo Tobi ethernet support
>
> Prafulla Wadaskar (2):
> Kirkwood: rd6281a: Add kwbimage build support
> Kirkwood: mv88f6281gtw_ge: Add kwbimage build support
>
> Sandeep Paulraj (9):
> TI DaVinci: Remove references to SZ_xx
> TI DaVinci: DM6446: Fix Compilation error in NAND mode
> TI DaVinci: DM646x: Initial Support for DM646x SOC
> TI DaVinci: DM355: Config Cleanup and Update
> TI DaVinci DM365: Removing header file which does not exist
> TI: DaVinci DM365: Minor config cleanup
> TI: DaVinci DM646x: Update flag used to represent DM646x SOC's
> TI: DaVinci: GPIO header file and definitions
> TI: DaVinci DM365: Enabling network Support on DM365 EVM
>
> Simon Kagstrom (2):
> Support for the OpenRD base board
> arm: Correct build with CONFIG_SYS_HUSH_PARSER set
>
> Tom Rix (4):
> OMAP3 Move cache routine to cache.S
> Add support for Eukrea CPUAT91 SBC
> Add support for Eukrea CPU9260/CPU9G20 SBC
> TI OMAP3 Use arm init sequence to initialize i2c
>
Tom,
Why this pull request does not include this[1] "sub pull request" from
samsung repository?
[1]: http://lists.denx.de/pipermail/u-boot/2009-October/062364.html
Thanks
next prev parent reply other threads:[~2009-10-13 13:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-13 12:55 [U-Boot] ARM pull request v3 Tom Rix
2009-10-13 13:34 ` Abdoulaye Walsimou Gaye [this message]
2009-10-13 14:04 ` Wolfgang Denk
2009-10-13 14:40 ` Paulraj, Sandeep
2009-10-13 14:51 ` Wolfgang Denk
2009-10-13 14:58 ` Simon Kagstrom
2009-10-14 11:18 ` Tom Rix
2009-10-14 11:54 ` Simon Kagstrom
2009-10-13 16:01 ` Dirk Behme
2009-10-13 16:08 ` Paulraj, Sandeep
2009-10-17 5:52 ` Dirk Behme
2009-10-17 13:25 ` Paulraj, Sandeep
2009-10-17 14:22 ` Tom
2009-10-17 22:16 ` Tom
-- strict thread matches above, loose matches on Subject: below --
2009-10-18 22:58 Tom
2009-10-19 0:37 ` Paulraj, Sandeep
2009-10-19 1:53 ` Ben Warren
2009-10-19 8:33 ` Wolfgang Denk
2009-10-19 14:38 ` Dirk Behme
2009-10-20 12:24 ` Tom
2009-10-23 9:28 ` Simon Kagstrom
2009-10-23 13:02 ` Tom
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=4AD481E4.9050200@walsimou.com \
--to=walsimou@walsimou.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