public inbox for linux-tegra@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
Cc: arm-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [GIT PULL V2] ARM: tegra: core SoC support changes for 3.13
Date: Fri, 25 Oct 2013 03:51:52 -0700	[thread overview]
Message-ID: <87sivppqrb.fsf@linaro.org> (raw)
In-Reply-To: <1382136027-4937-1-git-send-email-swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org> (Stephen Warren's message of "Fri, 18 Oct 2013 16:40:27 -0600")

Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org> writes:

> This branch includes:
> * SoC fuse values are used as device randomness at boot.
> * Initial support for the Tegra124 SoC is added. When coupled with an
>   appropriate clock driver, which should also be merged for 3.13, we are
>   able to boot to user-space using an initrd.
> * The powergate code gains support for Tegra114.
>
> This branch is based on previous pull request tegra-for-3.13-cleanup.
>
> ----------------------------------------------------------------
>
> The following changes since commit b6bda4e0d23815cb711c16085e03cb23c6d49f21:
>
>   ARM: tegra: fix ARCH_TEGRA_114_SOC select sort order
>
> are available in the git repository at:
>
>   git://git.kernel.org/pub/scm/linux/kernel/git/swarren/linux-tegra.git tegra-for-3.13-soc-v2
>
> for you to fetch changes up to bd6a9ddcb9f2cb19dae0509341a4cbaf40dc66f0:
>
>   ARM: tegra: Add Tegra114 powergate support
>
> ----------------------------------------------------------------

Thanks for the respin, pulled into next/soc.

Kevin 

      parent reply	other threads:[~2013-10-25 10:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-18 22:40 [GIT PULL V2] ARM: tegra: core SoC support changes for 3.13 Stephen Warren
     [not found] ` <1382136027-4937-1-git-send-email-swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-10-25 10:51   ` 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=87sivppqrb.fsf@linaro.org \
    --to=khilman-qsej5fyqhm4dnm+yrofe0a@public.gmane.org \
    --cc=arm-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.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