From: Tom Rix <tom@bumblecow.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Please pull u-boot-samsung/master
Date: Tue, 13 Oct 2009 22:31:04 -0500 [thread overview]
Message-ID: <4AD545F8.2030708@bumblecow.com> (raw)
In-Reply-To: <4AD2DCE3.5010108@samsung.com>
Minkyu Kang wrote:
> Dear Tom,
>
> The following changes since commit 617da90c1dcf65428ddfb63fef897439950bc915:
> Tom Rix (1):
> Merge branch 't-next-marvell' into t-next-at91
>
> are available in the git repository at:
>
> git://git.denx.de/u-boot-samsung master
>
> Minkyu Kang (5):
> s5pc1xx: support Samsung s5pc1xx SoC
> s5pc1xx: support onenand driver
> s5pc1xx: support serial driver
> s5pc1xx: add support SMDKC100 board
> Merge branch 'master' of git://git.denx.de/u-boot-arm
>
This is a new board.
I think this board was submitted after the merge window
And it has a lot of compiler warnings.
Can you clean these up ?
I think these should wait to be merged.
> kevin.morfitt at fearnside-systems.co.uk (5):
> CONFIG_SYS_HZ fix for ARM902T S3C24X0 Boards
> Clean-up of cpu_arm920t and cpu_arm920t_s3c24x0 code
> Clean-up of s3c24x0 header files
> Clean-up of s3c24x0 drivers excluding nand driver
> Clean-up of s3c24x0 nand driver
These look like a code that was run through indent.
cleaning up without any obvious new features.
These would be ok to merge.
Does this sound ok?
I can just cherry pick the cleanups.
Tom
next prev parent reply other threads:[~2009-10-14 3:31 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 7:38 [U-Boot] Please pull u-boot-samsung/master Minkyu Kang
2009-10-12 11:16 ` Tom Rix
2009-10-14 3:31 ` Tom Rix [this message]
2009-10-14 10:16 ` Abdoulaye Walsimou Gaye
2009-10-14 11:28 ` Stefan Roese
2009-10-14 12:39 ` Tom Rix
2009-10-14 12:46 ` Tom Rix
2009-10-14 13:23 ` Minkyu Kang
-- strict thread matches above, loose matches on Subject: below --
2009-11-20 10:45 Minkyu Kang
2009-11-20 22:16 ` Tom
2010-01-13 4:25 Minkyu Kang
2010-01-15 13:28 ` Tom
2010-03-05 10:03 Minkyu Kang
2010-03-05 20:29 ` Tom
2010-03-08 6:08 ` Minkyu Kang
2010-03-12 19:43 ` Tom
2010-03-13 16:32 ` Tom
2010-04-13 10:02 Minkyu Kang
2010-04-17 22:07 ` Tom Rix
2010-06-02 23:55 Minkyu Kang
2010-06-06 11:44 ` Tom Rix
2010-06-09 0:08 ` Minkyu Kang
2010-06-15 4:23 ` Tom Rix
2010-08-03 7:54 Minkyu Kang
2010-08-03 22:35 ` Wolfgang Denk
2010-08-31 10:27 Minkyu Kang
2010-09-07 22:04 ` Wolfgang Denk
2010-10-28 7:29 Minkyu Kang
2010-10-29 19:48 ` Wolfgang Denk
2010-11-30 8:56 Minkyu Kang
2010-11-30 20:32 ` Wolfgang Denk
2011-01-27 12:29 Minkyu Kang
2011-01-27 22:11 ` Albert ARIBAUD
2011-03-24 6:58 Minkyu Kang
2011-03-24 13:57 ` Albert ARIBAUD
2011-03-25 2:02 ` Minkyu Kang
2011-03-25 7:23 ` Albert ARIBAUD
2011-03-25 9:59 ` Minkyu Kang
2011-03-26 14:59 ` Albert ARIBAUD
2011-05-26 5:22 Minkyu Kang
2011-05-26 5:49 ` Albert ARIBAUD
2011-05-26 6:24 ` Minkyu Kang
2011-05-26 8:13 ` Albert ARIBAUD
2011-05-26 10:40 ` Minkyu Kang
2011-05-26 10:43 Minkyu Kang
2011-05-26 10:59 ` Albert ARIBAUD
2011-08-19 5:34 [U-Boot] please " Minkyu Kang
2011-08-19 18:22 ` Albert ARIBAUD
2011-09-02 8:05 Minkyu Kang
2011-09-03 19:23 ` Albert ARIBAUD
2011-10-28 8:19 Minkyu Kang
2011-10-28 15:17 ` Albert ARIBAUD
2011-12-09 9:15 Minkyu Kang
2011-12-09 16:39 ` Albert ARIBAUD
2012-02-10 1:01 Minkyu Kang
2012-02-10 19:59 ` Albert ARIBAUD
2012-03-08 10:14 Minkyu Kang
2012-03-27 9:44 ` Minkyu Kang
2012-03-27 20:09 ` Albert ARIBAUD
2012-04-25 7:51 Minkyu Kang
2012-04-26 21:26 ` Albert ARIBAUD
2012-06-18 8:50 Minkyu Kang
2012-06-23 7:18 ` 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=4AD545F8.2030708@bumblecow.com \
--to=tom@bumblecow.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