qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Michal Privoznik <mprivozn@redhat.com>
To: "Daniel P. Berrange" <berrange@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 11:20:14 +0200	[thread overview]
Message-ID: <f0a4fbf1-a1dc-03c2-25ad-6eaf6bec96e4@redhat.com> (raw)
In-Reply-To: <20170906090442.GJ15510@redhat.com>

On 09/06/2017 11:04 AM, Daniel P. Berrange wrote:
> 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.

Sure. We prefer that in libvirt too. Let me respin v4.

Michal

      reply	other threads:[~2017-09-06  9:20 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
2017-09-06  9:20     ` Michal Privoznik [this message]

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=f0a4fbf1-a1dc-03c2-25ad-6eaf6bec96e4@redhat.com \
    --to=mprivozn@redhat.com \
    --cc=armbru@redhat.com \
    --cc=berrange@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 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).