All of lore.kernel.org
 help / color / mirror / Atom feed
From: khilman@kernel.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: mvebu: fixes changes for v4.1
Date: Wed, 01 Jul 2015 13:42:13 -0700	[thread overview]
Message-ID: <7hzj3flie2.fsf@deeprootsystems.com> (raw)
In-Reply-To: <55832147.1020202@free-electrons.com> (Gregory CLEMENT's message of "Thu, 18 Jun 2015 21:51:35 +0200")

Gregory CLEMENT <gregory.clement@free-electrons.com> writes:

> Hi,
>
> Here is the forth pull request for fixes for mvebu for v4.1.
>
> Actually this bug can happen only on one board: the Armada XP GP,
> so if you can't pull it for 4.1, I will send it again once 4.2-rc1
> will be released.
>
> Gregory
>
> The following changes since commit 885dbd154b2f2ee305cec6fd0a162e1a77ae2b06:
>
>   Revert "bus: mvebu-mbus: make sure SDRAM CS for DMA don't overlap the MBus bridge window" (2015-05-28 11:14:31 +0200)
>
> are available in the git repository at:
>
>   git://git.infradead.org/linux-mvebu.git tags/mvebu-fixes-4.1-4
>
> for you to fetch changes up to 2f5bc307be2480ba89e4c5d118f406f04a4a7299:
>
>   ARM: mvebu: fix suspend to RAM on big-endian configurations (2015-06-17 17:23:36 +0200)
>
> ----------------------------------------------------------------
> mvebu fixes for 4.1 (part 4)
>
> Fix suspend to RAM on big-endian configurations on Armada XP GP board
>
> ----------------------------------------------------------------

Ignoring this one as I see you have an updated pull which includes this
and another patch.

Kevin

      reply	other threads:[~2015-07-01 20:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-18 19:51 [GIT PULL] ARM: mvebu: fixes changes for v4.1 Gregory CLEMENT
2015-07-01 20:42 ` 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=7hzj3flie2.fsf@deeprootsystems.com \
    --to=khilman@kernel.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.