mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: Diogo Ivo <diogo.ivo@siemens.com>,
	linux-watchdog@vger.kernel.org, linux-acpi@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
	"Benedikt Niedermayr" <benedikt.niedermayr@siemens.com>,
	"Günter Röck" <linux@roeck-us.net>,
	"Jan Kiszka" <jan.kiszka@siemens.com>,
	"Len Brown" <lenb@kernel.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	"Wim Van Sebroeck" <wim@linux-watchdog.org>
Subject: Re: [PATCH v3 1/2] watchdog: Add driver for Intel OC WDT
Date: Thu, 27 Mar 2025 14:56:34 +0100	[thread overview]
Message-ID: <1584e54b-8ab9-41b0-8cb3-19ba3abf10af@web.de> (raw)
In-Reply-To: <20250317-ivo-intel_oc_wdt-v3-1-32c396f4eefd@siemens.com>

> Add a driver for the Intel Over-Clocking Watchdog found in Intel
> Platform Controller (PCH) chipsets. This watchdog is controlled
…

You may occasionally put more than 64 characters into text lines
of such a change description.

Regards,
Markus

  reply	other threads:[~2025-03-27 13:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-17 10:55 [PATCH v3 0/2] Add driver for Intel Over-Clocking Watchdog Diogo Ivo
2025-03-17 10:55 ` [PATCH v3 1/2] watchdog: Add driver for Intel OC WDT Diogo Ivo
2025-03-27 13:56   ` Markus Elfring [this message]
2025-04-08  8:31   ` Diogo Ivo
2025-05-08 15:12     ` Diogo Ivo
2025-03-17 10:55 ` [PATCH v3 2/2] ACPI: PNP: Add Intel OC Watchdog IDs to non-PNP device list Diogo Ivo
2025-03-25 17:18   ` Diogo Ivo
2025-03-25 18:59     ` Rafael J. Wysocki
2025-03-26  9:01       ` Diogo Ivo
2025-03-26 14:02         ` Guenter Roeck
2025-03-27 19:36           ` Rafael J. Wysocki
2025-06-01 20:15 ` [PATCH v3 0/2] Add driver for Intel Over-Clocking Watchdog Andy Shevchenko
2025-06-03  9:43   ` Diogo Ivo

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=1584e54b-8ab9-41b0-8cb3-19ba3abf10af@web.de \
    --to=markus.elfring@web.de \
    --cc=benedikt.niedermayr@siemens.com \
    --cc=diogo.ivo@siemens.com \
    --cc=jan.kiszka@siemens.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=rafael@kernel.org \
    --cc=wim@linux-watchdog.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

all inboxes | Powered by JetHome®