public inbox for linux-arm-kernel@lists.infradead.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 for v4.2
Date: Wed, 01 Jul 2015 13:44:14 -0700	[thread overview]
Message-ID: <7hr3orliap.fsf@deeprootsystems.com> (raw)
In-Reply-To: <5592A03B.5020900@free-electrons.com> (Gregory CLEMENT's message of "Tue, 30 Jun 2015 15:57:15 +0200")

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

> Hi,
>
> Here is a small pull request for fixes for mvebu for v4.2.
> It would be nice to have them in v4.2-rc1. It combines two signed
> tags: the new one mvebu-fixes-4.2-0 and the previous one which has not
> been pulled for 4.1: mvebu-fixes-4.1-4
>
> 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.2-0
>
> for you to fetch changes up to 5d6bed2a9c8bc161bff4cc7cede00f2e0e27a7e7:
>
>   ARM: dove: fix legacy dove IRQ numbers (2015-06-24 11:05:57 +0200)
>
> ----------------------------------------------------------------
> mvebu fixes for 4.2 (part 0)
>
> Fix legacy dove IRQ numbers
>
> ----------------------------------------------------------------

Pulled into next/late, which might make it for -rc1, but if not, will
make it into -rc2.

Thanks,

Kevin

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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-30 13:57 [GIT PULL] ARM: mvebu: fixes for v4.2 Gregory CLEMENT
2015-07-01 20:44 ` 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=7hr3orliap.fsf@deeprootsystems.com \
    --to=khilman@kernel$(echo .)org \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox