From: Pratyush Anand <panand-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Pratyush Anand <panand-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Dave Young <dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Don Zickus <dzickus-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: [PATCH V5 dracut 0/3] Install kernel module for active watchdog
Date: Wed, 16 Mar 2016 09:09:08 +0530 [thread overview]
Message-ID: <cover.1458099200.git.panand@redhat.com> (raw)
Changes since V4:
-- Renamed 04watchdog.conf to 00watchdog.conf
Changes since V3:
-- Incorporated changes suggested by Harald for V2 patches
Changes since V2:
-- Added one more patch to update rd.driver.pre with watchdog module name,
so that they are loaded into kernel as early as possible.
-- Removed creation of tmp/active-watchdogs. modinfo will be helpful for
kexec-tools.
-- Now we add modules for active watchdog in hostonly mode and modules for
all watchdog in no-hostonly mode.
Changes since RFC:
-- Added one more patch to take care that dracut does not add watchdog
hooks when systemd module is included. In that case systemd daemon will
manage watchdog for kicking.
-- Removed --nowdt argument. User can use -o or --omit when wathdog module
is not needed. Thanks Harald for this suggestion.
-- Now I also do not check for "hostonly" to add modules for active
watchdog. It seems reasonable to add kernel watchdog modules whenever,
dracut watchdog module has been added.
Pratyush Anand (3):
watchdog: Do not add hooks if systemd module is included
watchdog: install module for active watchdog
watchdog: ensure that module is loaded as early as possible
Cc: Dave Young <dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Don Zickus <dzickus-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
modules.d/04watchdog/module-setup.sh | 38 ++++++++++++++++++++++++++++++++++++
1 file changed, 38 insertions(+)
--
2.5.0
next reply other threads:[~2016-03-16 3:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 3:39 Pratyush Anand [this message]
[not found] ` <cover.1458099200.git.panand-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-03-16 3:39 ` [PATCH V5 dracut 1/3] watchdog: Do not add hooks if systemd module is included Pratyush Anand
2016-03-16 3:39 ` [PATCH V5 dracut 2/3] watchdog: install module for active watchdog Pratyush Anand
2016-03-16 3:39 ` [PATCH V5 dracut 3/3] watchdog: ensure that module is loaded as early as possible Pratyush Anand
[not found] ` <2751555c29f26f69a63888745513edeceb39d416.1458099200.git.panand-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-03-16 4:05 ` [PATCH V5 dracut (Resend)3/3] " Dracut GitHub Import Bot
2016-03-16 4:18 ` [PATCH V5 dracut 3/3] " Pratyush Anand
[not found] ` <56E8DE95.4090308-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-03-17 14:08 ` Harald Hoyer
2016-04-15 9:54 ` [PATCH V5 dracut 0/3] Install kernel module for active watchdog Harald Hoyer
[not found] ` <5710BA3B.8030600-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-04-18 13:06 ` Pratyush Anand
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=cover.1458099200.git.panand@redhat.com \
--to=panand-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=dzickus-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 read-only IMAP folder(s) and NNTP newsgroup(s).