public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: robert.jarzmik@free.fr (Robert Jarzmik)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] pxa fixes for v4.8
Date: Tue, 09 Aug 2016 20:47:47 +0200	[thread overview]
Message-ID: <87fuqdvkx8.fsf@belgarion.home> (raw)


Hello Arnd, Kevin, Olof,

Please consider this pull request for pxa fixes for 4.8, made of 2 trivial
fixes. It's pretty unconventional, as I missed the 4.8-rc1 merge window, but
these are only 2 includes modifications, and it loosens the bond on gpio API for
future module.h include removal.

Let me know if you judge that safe enough as I did to let that in a -rc cycle.

The following changes since commit 29b4817d4018df78086157ea3a55c1d9424a7cfc:

  Linux 4.8-rc1 (2016-08-07 18:18:00 -0700)

are available in the git repository at:

  https://github.com/rjarzmik/linux.git tags/pxa-fixes-v4.8

for you to fetch changes up to a3c747b96df66a7eb810fef45f3b9e65614712d9:

  ARM: pxa: add module.h for corgi symbol_get/symbol_put usage (2016-08-09 08:19:06 +0200)

----------------------------------------------------------------
This is the pxa changes for v4.8 cycle.

This is a tiny fix couple to enable changes in includes in
gpio API without breaking pxa boards.

----------------------------------------------------------------
Paul Gortmaker (2):
      ARM: pxa: add module.h for spitz symbol_get/symbol_put usage
      ARM: pxa: add module.h for corgi symbol_get/symbol_put usage

 arch/arm/mach-pxa/corgi.c | 1 +
 arch/arm/mach-pxa/spitz.c | 1 +
 2 files changed, 2 insertions(+)

Cheers.

-- 
Robert

             reply	other threads:[~2016-08-09 18:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-09 18:47 Robert Jarzmik [this message]
2016-08-10 20:49 ` [GIT PULL] pxa fixes for v4.8 Arnd Bergmann

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=87fuqdvkx8.fsf@belgarion.home \
    --to=robert.jarzmik@free.fr \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox