mbox

[GIT,PULL,v2] Renesas ARM-based SoC boards for v3.8 #3

Message ID 1353372187-2903-1-git-send-email-horms@verge.net.au
State New
Headers show

Pull-request

git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git boards3

Message

Simon Horman Nov. 20, 2012, 12:43 a.m. UTC
Hi Olof, Hi Arnd,

Please consider the following board fix for 3.8.

The commit message for the patch has been revised since yesterday's
pull-request.

Also, please let me know if you would prefer me to supply
this as a fixes branch as we are now in the 3.7-rc6 timeframe
where I understand that non-fix commits are no longer allowed for 3.8.

This commit is based on the renesas/boards2 branch of the arm-soc tree.

----------------------------------------------------------------
The following changes since commit 12818d82ccad9868a820dbb193b4f9b797cd02d4:

  ARM: shmobile: use FSI driver's audio clock on ap4evb (2012-11-08 17:52:05 +0900)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git boards3

for you to fetch changes up to 3042ac5731e6db441dfce85612da4aa3913dab3b:

  ARM: shmobile: mackerel: Add FLCTL IRQ resource (2012-11-20 09:14:43 +0900)

----------------------------------------------------------------
Bastian Hecht (1):
      ARM: shmobile: mackerel: Add FLCTL IRQ resource

 arch/arm/mach-shmobile/board-mackerel.c |    6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

Comments

Olof Johansson Nov. 21, 2012, 7:21 a.m. UTC | #1
On Tue, Nov 20, 2012 at 09:43:06AM +0900, Simon Horman wrote:
> Hi Olof, Hi Arnd,
> 
> Please consider the following board fix for 3.8.
> 
> The commit message for the patch has been revised since yesterday's
> pull-request.
> 
> Also, please let me know if you would prefer me to supply
> this as a fixes branch as we are now in the 3.7-rc6 timeframe
> where I understand that non-fix commits are no longer allowed for 3.8.
>
> This commit is based on the renesas/boards2 branch of the arm-soc tree.

It's not super-strictly "fixes only" at this point in the tree, but we really
want to make sure that we don't get any large pull requests from here on out.

For an update like this (adding one more patch on top of a previous branch),
this format is perfect since it allows us to just pull the same branch again,
really. So I've pulled this on top of the previous contents into next/boards2.


-Olof