All of lore.kernel.org
 help / color / mirror / Atom feed
From: khilman@linaro.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: mvebu: fixes for v3.13.x/v3.14-rc1
Date: Tue, 28 Jan 2014 10:15:41 -0800	[thread overview]
Message-ID: <87y520ug4y.fsf@paris.lan> (raw)
In-Reply-To: <20140127193434.GN29184@titan.lakedaemon.net> (Jason Cooper's message of "Mon, 27 Jan 2014 14:34:34 -0500")

Jason Cooper <jason@lakedaemon.net> writes:

> Kevin,
>
> Here's the pull we discussed earlier.  Sorry my "send pull requests"
> cron job failed me.
>
> As usual, been in -next (a little long this time ;-) ), incremental from
> tags/mvebu-fixes-3.13 to tags/mvebu-fixes-3.13-2 in the mvebu/fixes
> branch.
>
> thx,
>
> Jason.
>
> The following changes since commit f8b94beb7e6a374cb0de531b72377c49857b35ca:
>
>   i2c: mv64xxx: Document the newly introduced Armada XP A0 compatible (2014-01-14 02:09:17 +0000)
>
> are available in the git repository at:
>
>   git://git.infradead.org/linux-mvebu.git tags/mvebu-fixes-3.13-2
>
> for you to fetch changes up to 19e61d41404fe4094c2d54943dbf883d9bbca864:
>
>   ARM: mvebu: fix compilation warning on Armada 370 (i.e. non-SMP) (2014-01-21 00:55:47 +0000)
>
> ----------------------------------------------------------------
> mvebu fixes for v3.13 (incremental #2)
>
>  - allow building and booting DT and non-DT plat-orion SoCs
>  - catch proper return value for kirkwood_pm_init()
>  - properly check return of of_iomap to solve boot hangs (mirabox, others)
>  - remove a compile warning on Armada 370 with non-SMP.
>
> ----------------------------------------------------------------

Thanks, I've queued these up for v3.14-rc, but they won't show up in any
builds until -rc1 is out.

Kevin

      reply	other threads:[~2014-01-28 18:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-27 19:34 [GIT PULL] ARM: mvebu: fixes for v3.13.x/v3.14-rc1 Jason Cooper
2014-01-28 18:15 ` Kevin Hilman [this message]

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=87y520ug4y.fsf@paris.lan \
    --to=khilman@linaro.org \
    --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.