linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT_PULL 2/3] ARM: Keystone config for 4.11
Date: Sun, 29 Jan 2017 14:46:39 -0800	[thread overview]
Message-ID: <20170129224639.GG3133@localhost> (raw)
In-Reply-To: <1485039758-15248-2-git-send-email-ssantosh@kernel.org>

On Sat, Jan 21, 2017 at 03:02:37PM -0800, Santosh Shilimkar wrote:
> The following changes since commit 7ce7d89f48834cefece7804d38fc5d85382edf77:
> 
>   Linux 4.10-rc1 (2016-12-25 16:13:08 -0800)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/ssantosh/linux-keystone.git tags/keystone_config_for_4.11
> 
> for you to fetch changes up to a2735c3067e7c25c46433c1d73b97d4d4e512de8:
> 
>   ARM: Keystone: Enable ARCH_HAS_RESET_CONTROLLER (2017-01-19 09:36:08 -0800)
> 
> ----------------------------------------------------------------
> ARM: Keystone config support for 4.11
> 
> 	- Enable Reset controller and on chip MSM RAM support.
> 
> ----------------------------------------------------------------
> Suman Anna (2):
>       ARM: configs: keystone: Enable Generic on-chip SRAM driver
>       ARM: Keystone: Enable ARCH_HAS_RESET_CONTROLLER

If you had other bpatches for arch/arm/mach-*, I'd group the latter into the
same branch as that. Anyway, not a huge deal on just an off patch like this.

Merged into next/defconfig.


-Olof

  reply	other threads:[~2017-01-29 22:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-21 23:02 [GIT_PULL 1/3] ARM: Keystone DTS for 4.11 Santosh Shilimkar
2017-01-21 23:02 ` [GIT_PULL 2/3] ARM: Keystone config " Santosh Shilimkar
2017-01-29 22:46   ` Olof Johansson [this message]
2017-01-21 23:02 ` [GIT_PULL 3/3] SOC: Keystone driver SOC " Santosh Shilimkar
2017-01-29 22:47   ` Olof Johansson
2017-01-31  1:20     ` Santosh Shilimkar
2017-01-29 22:45 ` [GIT_PULL 1/3] ARM: Keystone DTS " Olof Johansson

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=20170129224639.GG3133@localhost \
    --to=olof@lixom.net \
    --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).