All of lore.kernel.org
 help / color / mirror / Atom feed
From: ezequiel.garcia@free-electrons.com (Ezequiel Garcia)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: mvebu: fixes for v3.12
Date: Wed, 2 Oct 2013 10:51:13 -0300	[thread overview]
Message-ID: <20131002135112.GA2621@localhost> (raw)
In-Reply-To: <20130920034613.GB11119@titan.lakedaemon.net>

On Thu, Sep 19, 2013 at 11:46:13PM -0400, Jason Cooper wrote:
> Guys,
> 
> We have a relatively long list of fixes this time around.  The two
> of_node_put()'s were left over from before the merge window (part of
> mvebu/fixes-non-critical).
> 
> The two for the Armada XP clocks are to fix booting v3.12-rc1 since the
> corresponding driver changes were merged at the last minute.  These were
> originally part of mvebu/dt for v3.12, but have since become fixes.
> 
> The other two just cropped up since v3.12-rc1 dropped.
> 
> thx,
> 
> Jason.
> 
> The following changes since commit 272b98c6455f00884f0350f775c5342358ebb73f:
> 
>   Linux 3.12-rc1 (2013-09-16 16:17:51 -0400)
> 
> are available in the git repository at:
> 
>   git://git.infradead.org/linux-mvebu.git tags/fixes-3.12
> 
> for you to fetch changes up to ddf7e399024aa908573a08d6339cefa6253b83db:
> 
>   ARM: kirkwood: Fix address of second XOR engine (2013-09-20 03:16:20 +0000)
> 
> ----------------------------------------------------------------
> mvebu fixes for v3.12
> 
>  - mvebu
>     - fix reference leaks by adding of_node_put()
>     - update Armada XP DT clock properties to restore booting
> 
>  - kirkwood
>     - add missing reg property for cpu at 0
>     - fix typo in address of second XOR engine
> 
> ----------------------------------------------------------------
> Andrew Lunn (1):
>       ARM: Kirkwood: Add missing DT reg property to cpu at 0
> 
> Ezequiel Garcia (2):
>       ARM: mvebu: Add the reference 25 MHz fixed-clock to Armada XP
>       ARM: mvebu: Add clock properties to Armada XP timer node
> 

For some reason, I'm not seeing the above two in v3.12-rc3.

Guys: what happened? We need these to boot successfully...

> Jisheng Zhang (2):
>       ARM: mvebu: add missing of_node_put() to fix reference leak
>       bus: mvebu: add missing of_node_put() to fix reference leak
> 
> Quentin Armitage (1):
>       ARM: kirkwood: Fix address of second XOR engine
> 
>  arch/arm/boot/dts/armada-xp.dtsi        | 11 +++++++++++
>  arch/arm/boot/dts/kirkwood.dtsi         |  3 ++-
>  arch/arm/mach-mvebu/coherency.c         |  8 +++++++-
>  arch/arm/mach-mvebu/pmsu.c              |  1 +
>  arch/arm/mach-mvebu/system-controller.c |  1 +
>  drivers/bus/mvebu-mbus.c                |  6 +++++-
>  6 files changed, 27 insertions(+), 3 deletions(-)
> 
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

-- 
Ezequiel Garc?a, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com

  parent reply	other threads:[~2013-10-02 13:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-20  3:46 [GIT PULL] ARM: mvebu: fixes for v3.12 Jason Cooper
2013-09-20 17:36 ` Olof Johansson
2013-09-20 17:58   ` Jason Cooper
2013-10-02 13:51 ` Ezequiel Garcia [this message]
2013-10-02 20:09   ` Olof Johansson

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=20131002135112.GA2621@localhost \
    --to=ezequiel.garcia@free-electrons.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.