From: Dirk Behme <dirk.behme@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] TI:OMAP: [PATCH 1/7] OMAP3 Beagle Update revision detection
Date: Sun, 24 Jan 2010 09:59:44 +0100 [thread overview]
Message-ID: <4B5C0C00.9070707@googlemail.com> (raw)
In-Reply-To: <4B5B8E51.8060204@windriver.com>
On 24.01.2010 01:03, Tom wrote:
> Khasim Syed Mohammed wrote:
>> From 2dce4d64339a26144eac2ed56eb664cc1ea527c7 Mon Sep 17 00:00:00 2001
Khasim: The 'From' line of your patch starts with an additional '>'
>From 2dce4d64339a2 ...
Could you check where this comes from? Maybe this confuses the mailing
list archive
http://lists.denx.de/pipermail/u-boot/2010-January/066629.html
?
And could you try to add a 'vX' version to the subject of your
patches? E.g.
[PATCH 1/7 v4] OMAP3 Bea ....
This would really help to identify the patch versions.
>> From: Syed Mohammed Khasim<khasim@ti.com>
>> Date: Mon, 18 Jan 2010 18:03:42 +0530
>> Subject: [PATCH] OMAP3 Beagle Update revision detection
>>
>> New BeagleBoard revision C4 uses a new ID. Update revision detection.
>>
>
> This patch set caused regressions in MAKEALL arm
Tom: On recent master a84b655fab2bc021fdafa91d1196cf826474cdd8 this
patch seems to compile fine (?)
Best regards
Dirk
> These must be fixed.
>
> omap3_beagle
> cmd_i2c.c:109: warning: missing braces around initializer
> cmd_i2c.c:109: warning: (near initialization for 'i2c_no_probes[0]')
> beagle.c: In function 'misc_init_r':
> beagle.c:143: warning: implicit declaration of function 'twl4030_pmrecv_vsel_cfg'
> beagle.c:152: warning: implicit declaration of function 'prcm_config_720mhz'
>
> The changes I asked from for 1/7 were done.
> Tom
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
>
next prev parent reply other threads:[~2010-01-24 8:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 13:54 [U-Boot] TI:OMAP: [PATCH 1/7] OMAP3 Beagle Update revision detection Khasim Syed Mohammed
2010-01-24 0:03 ` Tom
2010-01-24 8:59 ` Dirk Behme [this message]
2010-01-24 10:17 ` [U-Boot] [beagleboard] " Paul Menzel
2010-01-24 14:26 ` [U-Boot] " Wolfgang Denk
2010-01-24 19:16 ` Dirk Behme
2010-01-24 19:46 ` Wolfgang Denk
2010-02-06 7:28 ` Dirk Behme
-- strict thread matches above, loose matches on Subject: below --
2010-01-12 19:01 Khasim Syed Mohammed
2010-01-17 0:14 ` Tom
2010-01-18 11:51 ` Khasim Syed Mohammed
2010-01-18 13:07 ` 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=4B5C0C00.9070707@googlemail.com \
--to=dirk.behme@googlemail.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