From: p.zabel@pengutronix.de (Philipp Zabel)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Reset controller changes for v4.7: build fix and OXNAS driver
Date: Tue, 03 May 2016 10:52:28 +0200 [thread overview]
Message-ID: <1462265548.3617.6.camel@pengutronix.de> (raw)
Dear arm-soc maintainers,
this tag contains a stub for the device_reset() function as a build fix
for drivers that use this function when compiling without
CONFIG_RESET_CONTROLLER enabled, and a reset driver for OXNAS SoCs.
regards
Philipp
The following changes since commit 773fe72630c8aca874ec8a07ebacace4ae305a02:
reset: lpc18xx: get rid of global variables for restart notifier (2016-03-30 15:42:07 +0200)
are available in the git repository at:
git://git.pengutronix.de/git/pza/linux.git tags/reset-for-4.7-2
for you to fetch changes up to 4113652252fad972e0c191b1e536dc74a6faebdc:
reset: Add missing function stub for device_reset (2016-04-04 18:15:23 +0200)
----------------------------------------------------------------
Reset controller changes for v4.7
- add missing stub for device_reset
- add support for OXNAS SoCs
----------------------------------------------------------------
Daniel Lezcano (1):
reset: Add missing function stub for device_reset
Neil Armstrong (2):
reset: Add Oxford Semiconductor Reset Controller driver
dt-bindings: Add Oxford Semiconductor Reset Controller bindings
.../devicetree/bindings/reset/oxnas,reset.txt | 58 +++++++++
drivers/reset/Kconfig | 3 +
drivers/reset/Makefile | 1 +
drivers/reset/reset-oxnas.c | 136 +++++++++++++++++++++
include/linux/reset.h | 6 +
5 files changed, 204 insertions(+)
create mode 100644 Documentation/devicetree/bindings/reset/oxnas,reset.txt
create mode 100644 drivers/reset/reset-oxnas.c
next reply other threads:[~2016-05-03 8:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-03 8:52 Philipp Zabel [this message]
2016-05-09 14:33 ` [GIT PULL] Reset controller changes for v4.7: build fix and OXNAS driver Arnd Bergmann
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=1462265548.3617.6.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--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).