public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: khilman@linaro•org (Kevin Hilman)
To: linux-arm-kernel@lists•infradead.org
Subject: [GIT PULL] minor Versatile updates
Date: Tue, 14 Jan 2014 15:38:16 -0800	[thread overview]
Message-ID: <87bnze5e3b.fsf@linaro.org> (raw)
In-Reply-To: <CACRpkdZFDCScea24A=CnV+Yxv-nZGxFKfhQsbvMHbxywwatPsA@mail.gmail.com> (Linus Walleij's message of "Wed, 8 Jan 2014 09:00:31 +0100")

Linus Walleij <linus.walleij@linaro•org> writes:

> Hi ARM SoC folks,
>
> the following is just one minor cleanup and then defconfig changes to
> set the scene for future Versatile cleanup/multiplatform work.
>
> Please pull it in to ARM SoC, the defconfig changes are even post-rc1
> material in some sense.
>
> Yours,
> Linus Walleij
>
>
> The following changes since commit 319e2e3f63c348a9b66db4667efa73178e18b17d:
>
>   Linux 3.13-rc4 (2013-12-15 12:31:33 -0800)
>
> are available in the git repository at:
>
>   git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-integrator.git
> tags/versatile-for-v3.14
>
> for you to fetch changes up to 27d2adb5969eef7ff3bfeb2dc3b2064e3a124952:
>
>   ARM: versatile: enable LEDs by default (2013-12-20 18:22:49 +0100)
>
> ----------------------------------------------------------------
> Versatile patches for v3.14:
>
> - Move GPIO2 and GPIO3 to be registered from the core boardfile.
>
> - Update the defconfig.
>
> Defconfig changes:
>
> - Enable GPIOLIB and PL061 for the Versatile.
>
> - Build the Versatile using EABI.
>
> - Enable the new LEDs in the defconfig.
>
> ----------------------------------------------------------------

Pulled into next/soc.

Thanks,

Kevin

      reply	other threads:[~2014-01-14 23:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-08  8:00 [GIT PULL] minor Versatile updates Linus Walleij
2014-01-14 23:38 ` 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=87bnze5e3b.fsf@linaro.org \
    --to=khilman@linaro$(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