linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Santosh Shilimkar <santosh.shilimkar@oracle.com>
To: arm@kernel.org, linux-arm-kernel@lists.infradead.org
Cc: khilman@kernel.org, arnd@arndb.de, olof@lixom.net,
	linux-kernel@vger.kernel.org, santosh.shilimkar@oracle.com
Subject: [GIT PULL 2/3] SOC: Keystone SOC update for 4.16
Date: Wed, 27 Dec 2017 18:07:51 -0800	[thread overview]
Message-ID: <1514426872-5769-2-git-send-email-santosh.shilimkar@oracle.com> (raw)
In-Reply-To: <1514426872-5769-1-git-send-email-santosh.shilimkar@oracle.com>

The following changes since commit 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323:

  Linux 4.15-rc1 (2017-11-26 16:01:47 -0800)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/ssantosh/linux-keystone.git tags/keystone_driver_soc_for_4.16

for you to fetch changes up to aefc5818553680c50c9f6840e47c01b80edd9b3a:

  soc: ti: fix max dup length for kstrndup (2017-12-16 14:45:33 -0800)

----------------------------------------------------------------
SOC: Keystone Soc driver updates for 4.16

 - TI EMIF-SRAM driver
 - TI SCI print format fix
 - Navigator strndup lenth fix

----------------------------------------------------------------
Arnd Bergmann (1):
      memory: ti-emif-sram: remove unused variable

Dave Gerlach (2):
      Documentation: dt: Update ti,emif bindings
      memory: ti-emif-sram: introduce relocatable suspend/resume handlers

Ma Shimiao (1):
      soc: ti: fix max dup length for kstrndup

Nishanth Menon (1):
      firmware: ti_sci: Use %zu for size_t print format

 .../bindings/memory-controllers/ti/emif.txt        |  17 +-
 drivers/firmware/ti_sci.c                          |   4 +-
 drivers/memory/Kconfig                             |  10 +
 drivers/memory/Makefile                            |   8 +
 drivers/memory/Makefile.asm-offsets                |   5 +
 drivers/memory/emif-asm-offsets.c                  |  92 ++++++
 drivers/memory/emif.h                              |  17 ++
 drivers/memory/ti-emif-pm.c                        | 324 ++++++++++++++++++++
 drivers/memory/ti-emif-sram-pm.S                   | 334 +++++++++++++++++++++
 drivers/soc/ti/knav_qmss_queue.c                   |   4 +-
 include/linux/ti-emif-sram.h                       |  69 +++++
 11 files changed, 879 insertions(+), 5 deletions(-)
 create mode 100644 drivers/memory/Makefile.asm-offsets
 create mode 100644 drivers/memory/emif-asm-offsets.c
 create mode 100644 drivers/memory/ti-emif-pm.c
 create mode 100644 drivers/memory/ti-emif-sram-pm.S
 create mode 100644 include/linux/ti-emif-sram.h

  reply	other threads:[~2017-12-28  2:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-28  2:07 [GIT PULL 1/3] ARM: Keystone DTS for 4.16 Santosh Shilimkar
2017-12-28  2:07 ` Santosh Shilimkar [this message]
2018-01-05  7:13   ` [GIT PULL 2/3] SOC: Keystone SOC update " Olof Johansson
2017-12-28  2:07 ` [GIT PULL 3/3] ARM: Keystone config " Santosh Shilimkar
2018-01-05  7:14   ` Olof Johansson
2018-01-05  7:12 ` [GIT PULL 1/3] ARM: Keystone DTS " Olof Johansson
2018-01-05 18:45   ` 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=1514426872-5769-2-git-send-email-santosh.shilimkar@oracle.com \
    --to=santosh.shilimkar@oracle.com \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=khilman@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olof@lixom.net \
    /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).