mbox

[GIT,PULL] Veratile Express DT updates for v3.5

Message ID 1337589524.2262.4.camel@hornet
State New
Headers show

Pull-request

git://git.linaro.org/people/pawelmoll/linux.git vexpress-v3.4

Message

Pawel Moll May 21, 2012, 8:38 a.m. UTC
Hi Arnd, Ofof,

Could you, please, pull this micro-updated for Versatile Express?
These are mostly DT changes related to A!5's architected timers and
VGIC. I have dropped the earlyprintk/uncompress patch for now because
Russell didn't like it.

Much more to come for 3.6 :-)

Thanks and apologies about short notice!

Pawel

The following changes since commit 76e10d158efb6d4516018846f60c2ab5501900bc:

  Linux 3.4 (2012-05-20 15:29:13 -0700)

are available in the git repository at:

  git://git.linaro.org/people/pawelmoll/linux.git vexpress-v3.4

for you to fetch changes up to c533f32e1ac440b8840159f89ece8c9cca2422b5:

  ARM: vexpress: Remove twice included header files (2012-05-21 09:30:42 +0100)

----------------------------------------------------------------
Pawel Moll (1):
      ARM: vexpress: Device Tree updates

Thomas Weber (1):
      ARM: vexpress: Remove twice included header files

 arch/arm/boot/dts/vexpress-v2p-ca15-tc1.dts |   13 ++++++++++++-
 arch/arm/boot/dts/vexpress-v2p-ca5s.dts     |   13 +++++++++----
 arch/arm/boot/dts/vexpress-v2p-ca9.dts      |    9 +++++++--
 arch/arm/mach-vexpress/v2m.c                |    2 --
 4 files changed, 28 insertions(+), 9 deletions(-)

Comments

Olof Johansson May 26, 2012, 8:46 a.m. UTC | #1
Hi Pawel,

On Mon, May 21, 2012 at 1:38 AM, Pawel Moll <pawel.moll@arm.com> wrote:
> Hi Arnd, Ofof,
>
> Could you, please, pull this micro-updated for Versatile Express?
> These are mostly DT changes related to A!5's architected timers and
> VGIC. I have dropped the earlyprintk/uncompress patch for now because
> Russell didn't like it.
>
> Much more to come for 3.6 :-)
>
> Thanks and apologies about short notice!

Since this is the first time you're late with a pull request, and the
branch is small, I'll cut you some slack. However, next time we get a
pull request like this after the merge window is open, I will punt it
until the next release.

So, I'll queue this up in late/soc and send it up sometime next week.
If the merge window closes early this means it _could_ miss it, but
hopefully not.


To avoid this from happening next time, please make sure the pull
requests reach us by -rc6 or -rc7 time frame.


Thanks,

-Olof
Pawel Moll May 29, 2012, 3:41 a.m. UTC | #2
Hi Olof,

> Since this is the first time you're late with a pull request, and the

> branch is small, I'll cut you some slack. However, next time we get a

> pull request like this after the merge window is open, I will punt it

> until the next release.


Shame on me, I do apologise. I was indeed planning to push it out in the
week after rc7, but got distracted so had to count on some mercy ;-)

> So, I'll queue this up in late/soc and send it up sometime next week.

> If the merge window closes early this means it _could_ miss it, but

> hopefully not.


I really appreciate it, thanks!

Paweł

-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium.  Thank you.