Linux Renesas SOC kernel development
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: linux-renesas-soc@vger.kernel.org
Cc: Geert Uytterhoeven <geert@linux-m68k.org>
Subject: [PULL REQUEST] renesas/topic/pretimeout for renesas drivers
Date: Sun, 29 May 2016 17:45:31 +0200	[thread overview]
Message-ID: <20160529154528.GA6451@katana> (raw)

[-- Attachment #1: Type: text/plain, Size: 2634 bytes --]

Hi Geert,

here is a topic branch for renesas-drivers. Please pull.

Kind regards,

   Wolfram


The following changes since commit 2dcd0af568b0cf583645c8a317dd12e344b1c72a:

  Linux 4.6 (2016-05-15 15:43:13 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git renesas/topic/pretimeout

for you to fetch changes up to 192d88ad087a1f20505c3249c6d51992d9f3caa8:

  watchdog: pretimeout: add userspace notifier pretimeout governor (2016-05-25 15:35:15 +0200)

----------------------------------------------------------------
Vladimir Zapolskiy (3):
      watchdog: pretimeout: add panic pretimeout governor
      watchdog: pretimeout: add noop pretimeout governor
      watchdog: pretimeout: add userspace notifier pretimeout governor

Wolfram Sang (13):
      watchdog: softdog: remove obsolete comments
      watchdog: softdog: use watchdog core to init timeout value
      watchdog: softdog: consistently use softdog_ prefix
      watchdog: softdog: remove forward declaration
      watchdog: softdog: sort includes to avoid duplicates
      watchdog: softdog: drop superfluous set_timeout callback
      watchdog: softdog: improve coding style
      watchdog: add watchdog pretimeout framework
      watchdog: documentation: squash paragraphs about 'no set_timeout'
      watchdog: add pretimeout support to the core
      fs: compat_ioctl: add pretimeout functions for watchdogs
      watchdog: softdog: implement pretimeout support
      watchdog: dev: add helper for creating uevent on dev

 Documentation/watchdog/watchdog-kernel-api.txt |  24 ++-
 drivers/watchdog/Kconfig                       |  68 +++++++
 drivers/watchdog/Makefile                      |  10 +-
 drivers/watchdog/pretimeout_noop.c             |  47 +++++
 drivers/watchdog/pretimeout_panic.c            |  47 +++++
 drivers/watchdog/pretimeout_userspace.c        |  47 +++++
 drivers/watchdog/softdog.c                     | 110 ++++------
 drivers/watchdog/watchdog_dev.c                |  81 +++++++-
 drivers/watchdog/watchdog_pretimeout.c         | 269 +++++++++++++++++++++++++
 drivers/watchdog/watchdog_pretimeout.h         |  43 ++++
 fs/compat_ioctl.c                              |   2 +
 include/linux/watchdog.h                       |  24 +++
 12 files changed, 695 insertions(+), 77 deletions(-)
 create mode 100644 drivers/watchdog/pretimeout_noop.c
 create mode 100644 drivers/watchdog/pretimeout_panic.c
 create mode 100644 drivers/watchdog/pretimeout_userspace.c
 create mode 100644 drivers/watchdog/watchdog_pretimeout.c
 create mode 100644 drivers/watchdog/watchdog_pretimeout.h

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

                 reply	other threads:[~2016-05-29 15:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20160529154528.GA6451@katana \
    --to=wsa@the-dreams.de \
    --cc=geert@linux-m68k.org \
    --cc=linux-renesas-soc@vger.kernel.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