Hi Linus,
this series was supposed to be pulled through various trees using it,
and I did not plan to send a separate pull request. As it turns out,
the pinctrl tree did not merge with it, is now upstream, and uses
it, meaning there are now build failures.
Please consider pulling this series directly to fix those build failures.
If you don't want to pull it directly, you should also get it through
the clk, power/reboot, and watchdog pull requests.
Thanks,
Guenter
------
The following changes since commit 52addcf9d6669fa439387610bc65c92fa0980cef:
Linux 3.17-rc2 (2014-08-25 15:36:20 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git
tags/restart-handler-for-v3.18
for you to fetch changes up to 6cd6d94d96d9b1cd8a62da91aac44cf56e301e75:
arm/arm64: unexport restart handlers (2014-09-26 00:00:48 -0700)
----------------------------------------------------------------
Immutable branch with restart handler patches for v3.18
----------------------------------------------------------------
Guenter Roeck (8):
kernel: add support for kernel restart handler call chain
power/restart: call machine_restart instead of arm_pm_restart
arm64: support restart through restart handler call chain
arm: support restart through restart handler call chain
watchdog: moxart: register restart handler with kernel restart handler
watchdog: alim7101: register restart handler with kernel restart handler
watchdog: sunxi: register restart handler with kernel restart handler
arm/arm64: unexport restart handlers
arch/arm/kernel/process.c | 12 +++--
arch/arm64/kernel/process.c | 3 +-
drivers/power/reset/restart-poweroff.c | 3 +-
drivers/watchdog/alim7101_wdt.c | 42 +++++++++++++-----
drivers/watchdog/moxart_wdt.c | 32 +++++++++-----
drivers/watchdog/sunxi_wdt.c | 31 ++++++++-----
include/linux/reboot.h | 3 ++
kernel/reboot.c | 81 ++++++++++++++++++++++++++++++++++
8 files changed, 165 insertions(+), 42 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
