All of lore.kernel.org
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] urgent omap related x86 pinctrl build fix for v3.13 merge window
Date: Fri, 18 Oct 2013 17:26:32 -0700	[thread overview]
Message-ID: <pull-1382142392-665487> (raw)

The following changes since commit dc7743aa3c49fabbc6dc9edbcf7df74d776ac32e:

  pinctrl: single: Add support for auxdata (2013-10-10 15:30:47 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v3.13/pinctrl-fix

for you to fetch changes up to 1b9c0fb365cbb1154f4e7997061db972cbf58300:

  pinctrl: single: Fix build when not built on ARM (2013-10-18 16:43:06 -0700)

----------------------------------------------------------------
Looks like I managed to break the x86 build for some
configs. Here's a fix for that on top of the pinctrl
changes already merged with the signed tag
omap-for-v3.13/quirk-signed.

----------------------------------------------------------------
Tony Lindgren (1):
      pinctrl: single: Fix build when not built on ARM

 drivers/pinctrl/pinctrl-single.c | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

             reply	other threads:[~2013-10-19  0:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-19  0:26 Tony Lindgren [this message]
     [not found] <5261d1f8.c348b40a.5cc9.08f4SMTPIN_ADDED_BROKEN@mx.google.com>
2013-10-19  0:32 ` [GIT PULL] urgent omap related x86 pinctrl build fix for v3.13 merge window Olof Johansson
2013-10-19  0:32   ` Olof Johansson
  -- strict thread matches above, loose matches on Subject: below --
2013-10-19  0:26 Tony Lindgren
2013-10-19  0:26 Tony Lindgren

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=pull-1382142392-665487 \
    --to=tony@atomide.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.