From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Jerry Hoemann <jerry.hoemann@hpe.com>
Cc: linux-renesas-soc@vger.kernel.org,
Jean-Marie Verdun <verdun@hpe.com>,
Nick Hawkins <nick.hawkins@hpe.com>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>,
linux-watchdog@vger.kernel.org
Subject: Re: [RFC PATCH 3/9] watchdog: hpe-wdt: don't print out if registering watchdog fails
Date: Sat, 5 Oct 2024 07:23:19 +0200 [thread overview]
Message-ID: <ZwDNR29rqWcLYlRZ@shikoro> (raw)
In-Reply-To: <ZwBeJUXqm3Tf0th_@anatevka.ftc.rdlabs.hpecorp.net>
[-- Attachment #1: Type: text/plain, Size: 747 bytes --]
On Fri, Oct 04, 2024 at 03:29:09PM -0600, Jerry Hoemann wrote:
> On Fri, Oct 04, 2024 at 10:03:06PM +0200, Wolfram Sang wrote:
> > The core will do this already.
> >
> > Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> > ---
> > drivers/watchdog/gxp-wdt.c | 4 +---
> > 1 file changed, 1 insertion(+), 3 deletions(-)
>
> Question: should email have been titled
> "watchdog: gxp-wdt: ..."
> instead of
> "watchdog: hpe-wdt: ..."
>
> to match the module name as the email title gets put into
> the git log for the file?
No objection, we can do that. I check git-log for the prefixes and found
there the following:
6b47441bed49 ("watchdog: hpe-wdt: Introduce HPE GXP Watchdog")
I am fine with both.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-10-05 5:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 20:03 [RFC PATCH 0/9] watchdog: don't print out if registering watchdog fails Wolfram Sang
2024-10-04 20:03 ` [RFC PATCH 1/9] watchdog: always print when " Wolfram Sang
2024-10-04 20:52 ` Guenter Roeck
2024-10-04 20:03 ` [RFC PATCH 2/9] watchdog: da9055_wdt: don't print out if " Wolfram Sang
2024-10-04 20:53 ` Guenter Roeck
2024-10-04 20:03 ` [RFC PATCH 3/9] watchdog: hpe-wdt: " Wolfram Sang
2024-10-04 20:53 ` Guenter Roeck
2024-10-04 21:29 ` Jerry Hoemann
2024-10-05 5:23 ` Wolfram Sang [this message]
2024-10-06 16:10 ` Jerry Hoemann
2024-10-04 20:03 ` [RFC PATCH 4/9] watchdog: iTCO_wdt: " Wolfram Sang
2024-10-04 20:53 ` Guenter Roeck
2024-10-04 20:03 ` [RFC PATCH 5/9] watchdog: it87_wdt: " Wolfram Sang
2024-10-04 20:53 ` Guenter Roeck
2024-10-04 20:03 ` [RFC PATCH 6/9] watchdog: octeon-wdt: " Wolfram Sang
2024-10-04 20:54 ` Guenter Roeck
2024-10-04 20:03 ` [RFC PATCH 7/9] watchdog: rti_wdt: " Wolfram Sang
2024-10-04 20:54 ` Guenter Roeck
2024-10-04 20:03 ` [RFC PATCH 8/9] watchdog: rza_wdt: " Wolfram Sang
2024-10-04 20:03 ` [RFC PATCH 9/9] watchdog: sl28cpld_wdt: " Wolfram Sang
2024-10-04 20:54 ` Guenter Roeck
2024-10-05 11:19 ` Michael Walle
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=ZwDNR29rqWcLYlRZ@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=jerry.hoemann@hpe.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=nick.hawkins@hpe.com \
--cc=verdun@hpe.com \
--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