From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PULL] u-boot-pxa/master
Date: Thu, 08 Mar 2012 08:12:57 +0100 [thread overview]
Message-ID: <4F585BF9.4080908@aribaud.net> (raw)
In-Reply-To: <201203061207.57158.marex@denx.de>
Hi Marek,
Le 06/03/2012 12:07, Marek Vasut a ?crit :
> Dear Albert ARIBAUD,
>
> The following changes since commit 3513896e57c6757c411e0633ccb5da08c36ad7d4:
>
> Fix erroneous 32-bit access to hw_clkctrl_frac0 and hw_clkctrl_frac1 registers
> (2012-03-05 13:36:36 +0100)
>
> are available in the git repository at:
>
> git://git.denx.de/u-boot-pxa.git master
>
> for you to fetch changes up to d85feeff3e8fc458654274835b2cf8e61070cdf4:
>
> IXP: Fix GPIO_INT_ACT_LOW_SET() (2012-03-06 11:57:43 +0100)
>
> ----------------------------------------------------------------
> Marek Vasut (7):
> Examples: Properly append LDFLAGS to LD command
> IXP: Make IXP buildable with arm-linux- toolchains
> IXP: Fix missing MACH_TYPE_{ACTUX?,PNB3,DVLHOST}
> IXP: Squash warnings in IXP NPE
> IXP: Move PDNB3 and SCPU from Makefile to boards.cfg
> IXP: Fix NAND build warning on PDNB3 and SCPU
> IXP: Fix GPIO_INT_ACT_LOW_SET()
>
> Makefile | 12 ------------
> arch/arm/cpu/ixp/config.mk | 3 +++
> arch/arm/cpu/ixp/npe/IxEthAcc.c | 2 +-
> arch/arm/cpu/ixp/npe/IxEthDBAPISupport.c | 3 ---
> arch/arm/cpu/ixp/npe/IxQMgrDispatcher.c | 3 ---
> arch/arm/include/asm/arch-ixp/ixp425.h | 10 ++++++++--
> board/actux1/actux1.c | 2 --
> board/actux2/actux2.c | 2 --
> board/actux3/actux3.c | 2 --
> board/actux4/actux4.c | 2 --
> board/dvlhost/dvlhost.c | 2 --
> board/prodrive/pdnb3/nand.c | 16 +++-------------
> board/prodrive/pdnb3/pdnb3.c | 3 ---
> boards.cfg | 2 ++
> examples/standalone/Makefile | 2 +-
> include/configs/actux1.h | 2 ++
> include/configs/actux2.h | 2 ++
> include/configs/actux3.h | 2 ++
> include/configs/actux4.h | 2 ++
> include/configs/dvlhost.h | 2 ++
> include/configs/pdnb3.h | 2 ++
> 21 files changed, 30 insertions(+), 48 deletions(-)
>
> Best regards,
> Marek Vasut
Applied to u-boot-arm/master, thanks!
Amicalement,
--
Albert.
next prev parent reply other threads:[~2012-03-08 7:12 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 11:07 [U-Boot] [PULL] u-boot-pxa/master Marek Vasut
2012-03-08 7:12 ` Albert ARIBAUD [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-10-16 5:16 Marek Vasut
2012-10-16 16:17 ` Albert ARIBAUD
2013-06-12 20:57 Marek Vasut
2013-06-13 11:04 ` Albert ARIBAUD
2013-06-22 13:26 Marek Vasut
2013-06-22 16:57 ` Albert ARIBAUD
2013-06-22 17:42 ` Mike Dunn
2013-06-22 19:21 ` Albert ARIBAUD
2013-06-23 9:05 ` Marek Vasut
2013-06-23 10:13 ` Albert ARIBAUD
2013-06-23 16:41 ` Mike Dunn
2013-06-23 19:46 ` Marek Vasut
2013-06-28 8:31 ` Albert ARIBAUD
2013-12-18 17:17 Marek Vasut
2013-12-18 18:47 ` Albert ARIBAUD
2013-12-18 18:55 ` Marek Vasut
2013-12-18 19:35 ` Tom Rini
2013-12-18 19:40 ` Marek Vasut
2013-12-18 21:02 ` Marek Vasut
2013-12-18 22:06 ` Albert ARIBAUD
2014-01-13 11:42 Marek Vasut
2014-01-13 13:16 ` Albert ARIBAUD
2014-01-13 16:41 ` Albert ARIBAUD
2014-02-06 1:54 Marek Vasut
2014-02-19 8:03 ` Albert ARIBAUD
2015-03-02 10:04 Marek Vasut
2015-03-02 15:28 ` Tom Rini
2015-08-24 18:31 Marek Vasut
2015-08-25 2:15 ` Tom Rini
2016-11-23 12:54 Marek Vasut
2016-11-23 18:07 ` Tom Rini
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=4F585BF9.4080908@aribaud.net \
--to=albert.u.boot@aribaud.net \
--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