mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Artem Novak <artem122novak@gmail.com>
Cc: bcm-kernel-feedback-list@broadcom.com,
	florian.fainelli@broadcom.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	linux-rpi-kernel@lists.infradead.org,
	linux-watchdog@vger.kernel.org, wim@linux-watchdog.org
Subject: Re: [PATCH v2] watchdog: bcm2835: add newline to dev_info message
Date: Sun, 22 Nov 2026 08:15:46 -0800	[thread overview]
Message-ID: <e9a71a95-3b8d-4e69-aefa-174446b1b19a@roeck-us.net> (raw)
In-Reply-To: <20261122102328.207524-1-artem122novak@gmail.com>

On Sun, Nov 22, 2026 at 04:23:28AM -0600, Artem Novak wrote:
> Add a newline to the watchdog timer initialization message so that
> the message is properly terminated in the kernel log.
> 
> Signed-off-by: Artem Novak <artem122novak@gmail.com>

Applied.

> ---

For future patches: Change log goes here.

Thanks,
Guenter

>  drivers/watchdog/bcm2835_wdt.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/watchdog/bcm2835_wdt.c b/drivers/watchdog/bcm2835_wdt.c
> index 755954cbadee..df08236d2689 100644
> --- a/drivers/watchdog/bcm2835_wdt.c
> +++ b/drivers/watchdog/bcm2835_wdt.c
> @@ -213,7 +213,7 @@ static int bcm2835_wdt_probe(struct platform_device *pdev)
>  					      SYS_OFF_PRIO_DEFAULT,
>  					      bcm2835_power_off, wdt);
>  
> -	dev_info(dev, "Broadcom BCM2835 watchdog timer");
> +	dev_info(dev, "Broadcom BCM2835 watchdog timer\n");
>  	return 0;
>  }
>  

      reply	other threads:[~2026-11-22 16:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-22  8:29 [PATCH] " Artem Novak
2026-11-22 10:08 ` Guenter Roeck
2026-11-22 10:23 ` [PATCH v2] " Artem Novak
2026-11-22 16:15   ` Guenter Roeck [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=e9a71a95-3b8d-4e69-aefa-174446b1b19a@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=artem122novak@gmail.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=florian.fainelli@broadcom.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=linux-watchdog@vger.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®