All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [PATCH 2/2] watchdog: generic name for i6300esb
Date: Tue, 10 Jun 2025 18:12:12 +0100	[thread overview]
Message-ID: <aEhnbN1pSYgdi4EZ@redhat.com> (raw)
In-Reply-To: <20250610143259.1056400-3-cohuck@redhat.com>

On Tue, Jun 10, 2025 at 04:32:59PM +0200, Cornelia Huck wrote:
> The Intel 6300 Enterprise SouthBridge is a south bridge for a more or
> less obscure embedded Intel system; however, the i6300esb watchdog
> device we implement in QEMU is a virtual watchdog device that should
> work well on any PCI-based machine, is well supported by Linux guests,
> and used in many examples on how to set up a virtual watchdog.
> 
> Let's use "virtual i6300ESB" in the description to make clear that
> this device will work just fine on non-Intel platforms.
> 
> Signed-off-by: Cornelia Huck <cohuck@redhat.com>
> ---
>  hw/watchdog/wdt_i6300esb.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

I'm not entirely sold on the idea that this is needed, but at the same
time I won't object so

Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>


> 
> diff --git a/hw/watchdog/wdt_i6300esb.c b/hw/watchdog/wdt_i6300esb.c
> index bb8a2766b69b..5e5d8c48cfd7 100644
> --- a/hw/watchdog/wdt_i6300esb.c
> +++ b/hw/watchdog/wdt_i6300esb.c
> @@ -472,7 +472,7 @@ static void i6300esb_class_init(ObjectClass *klass, const void *data)
>      device_class_set_legacy_reset(dc, i6300esb_reset);
>      dc->vmsd = &vmstate_i6300esb;
>      set_bit(DEVICE_CATEGORY_WATCHDOG, dc->categories);
> -    dc->desc = "Intel 6300ESB";
> +    dc->desc = "virtual i6300ESB";
>  }
>  
>  static const TypeInfo i6300esb_info = {
> -- 
> 2.49.0
> 
> 

With 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 :|



  reply	other threads:[~2025-06-10 17:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-10 14:32 [PATCH 0/2] cosmetics for the i6300esb watchdog Cornelia Huck
2025-06-10 14:32 ` [PATCH 1/2] watchdog: CONFIG_WDT_IB6300ESB -> CONFIG_WDT_I6300ESB Cornelia Huck
2025-06-10 17:11   ` Daniel P. Berrangé
2025-06-10 14:32 ` [PATCH 2/2] watchdog: generic name for i6300esb Cornelia Huck
2025-06-10 17:12   ` Daniel P. Berrangé [this message]
2025-07-15 12:17     ` Andrea Bolognani
2025-07-15 15:44       ` Cornelia Huck
2025-07-15 16:02         ` Daniel P. Berrangé
2025-07-15 16:16           ` Andrea Bolognani
2025-07-15 16:33             ` Daniel P. Berrangé
2025-07-17 15:17               ` Cornelia Huck
2025-07-17 15:49                 ` Daniel P. Berrangé
2025-07-29 16:01                   ` Cornelia Huck
2025-07-29 16:09                     ` Daniel P. Berrangé
2025-07-30  7:53                       ` Cornelia Huck
2025-07-18 14:35                 ` Yan Vugenfirer
2025-06-24 11:46 ` [PATCH 0/2] cosmetics for the i6300esb watchdog Cornelia Huck

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=aEhnbN1pSYgdi4EZ@redhat.com \
    --to=berrange@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@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.