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/2] SOC: Couple of drivers changes for v4.17
Date: Mon, 5 Mar 2018 16:41:13 -0800 [thread overview]
Message-ID: <1520296873-12982-2-git-send-email-santosh.shilimkar@oracle.com> (raw)
In-Reply-To: <1520296873-12982-1-git-send-email-santosh.shilimkar@oracle.com>
The following changes since commit 91ab883eb21325ad80f3473633f794c78ac87f51:
Linux 4.16-rc2 (2018-02-18 17:29:42 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/ssantosh/linux-keystone.git tags/soc_drivers_for_4.17
for you to fetch changes up to a817e5d82a2dc5daaa0a8a66cfab268fdf2f6bb6:
memory: ti-emif-sram: remove redundant dev_err call in ti_emif_probe() (2018-03-05 16:21:31 -0800)
----------------------------------------------------------------
SOC driver changes for v4.17
- Remove deundant dev_err from probe in ti-emif-srma driver
- Make use of seq_putc in emif reg show
----------------------------------------------------------------
SF Markus Elfring (1):
memory-EMIF: Use seq_putc() in emif_regdump_show()
Wei Yongjun (1):
memory: ti-emif-sram: remove redundant dev_err call in ti_emif_probe()
drivers/memory/emif.c | 2 +-
drivers/memory/ti-emif-pm.c | 1 -
2 files changed, 1 insertion(+), 2 deletions(-)
next prev parent reply other threads:[~2018-03-06 0:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-06 0:41 [GIT PULL 1/2] ARM: Keystone DTS " Santosh Shilimkar
2018-03-06 0:41 ` Santosh Shilimkar [this message]
2018-03-07 15:50 ` [GIT PULL 2/2] SOC: Couple of drivers changes " Arnd Bergmann
2018-03-07 16:54 ` 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=1520296873-12982-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
all inboxes | Powered by JetHome®