All of lore.kernel.org
 help / color / mirror / Atom feed
From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: mvebu: cleanup changes for v4.3
Date: Fri, 21 Aug 2015 17:50:56 +0200	[thread overview]
Message-ID: <55D748E0.3080004@free-electrons.com> (raw)

Hi,

Here is the first pull request for fixes for mvebu for v4.2.
I hope it is not too late, if it can't make ti for 4.2, then we
will apply it on 4.3, anyway the bug is here since 3.18.

Gregory

The following changes since commit d770e558e21961ad6cfdf0ff7df0eb5d7d4f0754:

  Linux 4.2-rc1 (2015-07-05 11:01:52 -0700)

are available in the git repository at:

  git://git.infradead.org/linux-mvebu.git tags/mvebu-fixes-4.2-1

for you to fetch changes up to 5be9fc23cdb42e1d383ecc8eae8a8ff70a752708:

  ARM: orion5x: fix legacy orion5x IRQ numbers (2015-08-21 17:33:08 +0200)

----------------------------------------------------------------
mvebu fixes changes for v4.2

Fix legacy orion5x IRQ numbers broken since 3.18

----------------------------------------------------------------
Benjamin Cama (1):
      ARM: orion5x: fix legacy orion5x IRQ numbers

 arch/arm/Kconfig                          |  1 +
 arch/arm/mach-orion5x/include/mach/irqs.h | 64 +++++++++++++++----------------
 arch/arm/mach-orion5x/irq.c               |  4 +-
 3 files changed, 35 insertions(+), 34 deletions(-)

-- 
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

             reply	other threads:[~2015-08-21 15:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-21 15:50 Gregory CLEMENT [this message]
2015-08-21 15:53 ` [GIT PULL] ARM: mvebu: cleanup changes for v4.3 Gregory CLEMENT
2015-08-21 16:12 ` Olof Johansson
  -- strict thread matches above, loose matches on Subject: below --
2015-07-16 22:09 Gregory CLEMENT
2015-07-17 17:07 ` 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=55D748E0.3080004@free-electrons.com \
    --to=gregory.clement@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.