From: Cornelia Huck <cohuck@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH 0/2] cosmetics for the i6300esb watchdog
Date: Tue, 24 Jun 2025 13:46:51 +0200 [thread overview]
Message-ID: <877c11icpg.fsf@redhat.com> (raw)
In-Reply-To: <20250610143259.1056400-1-cohuck@redhat.com>
On Tue, Jun 10 2025, Cornelia Huck <cohuck@redhat.com> wrote:
> The i6300esb watchdog device is generic enough to be used on any PCI
> platform; however, having an "Intel" device on a non-x86 platform looks
> a bit odd. Just call it a "virtual" device instead, and also fix an old
> typo for the config option while at it.
>
> Cornelia Huck (2):
> watchdog: CONFIG_WDT_IB6300ESB -> CONFIG_WDT_I6300ESB
> watchdog: generic name for i6300esb
>
> hw/watchdog/Kconfig | 2 +-
> hw/watchdog/meson.build | 2 +-
> hw/watchdog/wdt_i6300esb.c | 2 +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
Friendly ping -- any sentiment regarding those patches?
prev parent reply other threads:[~2025-06-24 11:48 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é
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 ` Cornelia Huck [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=877c11icpg.fsf@redhat.com \
--to=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.