From: "Daniel P. Berrange" <berrange@redhat.com>
To: Michal Privoznik <mprivozn@redhat.com>
Cc: qemu-devel@nongnu.org, armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3 2/2] watchdog: Allow setting action on the fly
Date: Wed, 6 Sep 2017 10:04:42 +0100 [thread overview]
Message-ID: <20170906090442.GJ15510@redhat.com> (raw)
In-Reply-To: <5defe9fcfacaae68ebbdb76b3ec4b565bf4e7d1c.1504688205.git.mprivozn@redhat.com>
On Wed, Sep 06, 2017 at 10:58:54AM +0200, Michal Privoznik wrote:
> Currently, the only time that users can set watchdog action is at
> the start as all we expose is this -watchdog-action command line
> argument. This is suboptimal when users want to plug the device
> later via monitor. Alternatively, they might want to change the
> action for already existing device on the fly.
>
> At the same time, drop local redefinition of the actions enum in
> watchdog.h in favour of the ones defined in schema and thus kills
> code duplication.
Nit-pick - I'd suggest 2 separat patches - one that drops the enum
redefinition, and the second which adds the new monitor command.
That way you separate no-op refactoring, from new features.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2017-09-06 9:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-06 8:58 [Qemu-devel] [PATCH v3 0/2] watchdog: Allow setting action on the fly Michal Privoznik
2017-09-06 8:58 ` [Qemu-devel] [PATCH v3 1/2] qapi: Rename WatchdogExpirationAction enum Michal Privoznik
2017-09-06 8:58 ` [Qemu-devel] [PATCH v3 2/2] watchdog: Allow setting action on the fly Michal Privoznik
2017-09-06 9:04 ` Daniel P. Berrange [this message]
2017-09-06 9:20 ` Michal Privoznik
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=20170906090442.GJ15510@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=mprivozn@redhat.com \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.