From: khilman@linaro.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/3] ARM: keystone: SOC updates for 3.14
Date: Thu, 19 Dec 2013 15:10:58 -0800 [thread overview]
Message-ID: <87sitoighp.fsf@linaro.org> (raw)
In-Reply-To: <1387230397-14338-2-git-send-email-santosh.shilimkar@ti.com> (Santosh Shilimkar's message of "Mon, 16 Dec 2013 16:46:36 -0500")
Hi Santosh,
Santosh Shilimkar <santosh.shilimkar@ti.com> writes:
> Arnd, Olof, Kevin,
>
> Please pull below keystone SOC updates for 3.14
>
> Regards,
> Santosh
>
> The following changes since commit 6ce4eac1f600b34f2f7f58f9cd8f0503d79e42ae:
>
> Linux 3.13-rc1 (2013-11-22 11:30:55 -0800)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/ssantosh/linux-keystone.git for_3.14/soc
>
> for you to fetch changes up to 8aad10f656470369b5802da422f68d4d31fcb865:
>
> ARM: keystone: defconfig: enable USB support (2013-12-16 16:03:36 -0500)
>
> ----------------------------------------------------------------
Any (good) reason you're not using signed tags?
> Keystone SOC updates for 3.14
>
> - Allow keystone kernel to be build in BE mode
> - Enabling DMA zone support
> - Removal of double of_clk_init
> - Enabling USB driver support in defconfig
>
> ----------------------------------------------------------------
Pulled into next/soc.
Thanks,
Kevin
next prev parent reply other threads:[~2013-12-19 23:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-16 21:46 [GIT PULL 1/3] ARM: keystone: device tree updates for 3.14 Santosh Shilimkar
2013-12-16 21:46 ` [GIT PULL 2/3] ARM: keystone: SOC " Santosh Shilimkar
2013-12-19 23:10 ` Kevin Hilman [this message]
2013-12-20 0:41 ` Santosh Shilimkar
2013-12-16 21:46 ` [GIT PULL 3/3] ARM: MAINTAINERS: " Santosh Shilimkar
2013-12-19 23:14 ` Kevin Hilman
2013-12-20 0:46 ` Santosh Shilimkar
2013-12-19 23:03 ` [GIT PULL 1/3] ARM: keystone: device tree " Kevin Hilman
2013-12-20 0:03 ` Santosh Shilimkar
2013-12-20 15:51 ` Kevin Hilman
2013-12-20 16:16 ` Santosh Shilimkar
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=87sitoighp.fsf@linaro.org \
--to=khilman@linaro.org \
--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;
as well as URLs for NNTP newsgroup(s).