From: Rob Herring <robherring2@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Any outstanding ARM pull requests?
Date: Thu, 08 Mar 2012 10:07:50 -0600 [thread overview]
Message-ID: <4F58D956.5090505@gmail.com> (raw)
In-Reply-To: <4F585DB9.8060901@aribaud.net>
On 03/08/2012 01:20 AM, Albert ARIBAUD wrote:
> Hi all,
>
> On my working repo where I have all ARM subrepos as remotes, a
>
> git branch -r --no-merged | grep '/master'
>
> with HEAD set to my master branch gives the following:
>
> u-boot-atmel/master
> u-boot-atmel/master-arm
> u-boot-imx/master
> u-boot-pxa/master
> u-boot-samsung/master
> u-boot-tegra/master
>
> Which means there are commmits on these repo's master branches that are
> not currently in u-boot-arm.
>
> Are there any ARM pull requests pending that I would have missed or are
> about to be sent?
>
> Amicalement,
The highbank fixes are still not applied. You can get them off the list
or here's a pull request again:
The following changes since commit 2acca35ce4604dcef933f07d90aa9c9c930e1049:
Merge branch 'master' of git://git.denx.de/u-boot-mmc (2012-02-17
23:54:46 +0100)
are available in the git repository at:
git://sources.calxeda.com/u-boot.git fixes
Rob Herring (4):
net: calxedaxgmac: fix build due to missing __aligned definition
ARM: highbank: fix warning for calxedaxgmac_initialize
ARM: highbank: add missing get_tbclk
ARM: highbank: fix us_to_tick calculation
arch/arm/cpu/armv7/highbank/timer.c | 9 +++++++--
board/highbank/highbank.c | 1 +
drivers/net/calxedaxgmac.c | 1 +
3 files changed, 9 insertions(+), 2 deletions(-)
Rob
next prev parent reply other threads:[~2012-03-08 16:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 7:20 [U-Boot] Any outstanding ARM pull requests? Albert ARIBAUD
2012-03-08 7:29 ` Stefano Babic
2012-03-08 8:06 ` Minkyu Kang
2012-03-08 16:02 ` Tom Warren
2012-03-08 21:05 ` Albert ARIBAUD
2012-03-08 16:07 ` Rob Herring [this message]
2012-03-28 18:15 ` Rob Herring
2012-03-28 21:35 ` 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=4F58D956.5090505@gmail.com \
--to=robherring2@gmail.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