From: Mukesh Ojha <mojha@codeaurora.org>
To: Colin King <colin.king@canonical.com>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
linux-watchdog@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] watchdog: intel_scu_watchdog: fix spelling mistake: "set_hearbeat" -> "set_heartbeat"
Date: Wed, 17 Apr 2019 12:01:20 +0530 [thread overview]
Message-ID: <8149cea7-d7dd-2907-3f85-caba792b7cf0@codeaurora.org> (raw)
In-Reply-To: <20190416133318.21045-1-colin.king@canonical.com>
On 4/16/2019 7:03 PM, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> There is a spelling mistake in a pr_debug message. Fix it.
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
Reviewed-by: Mukesh Ojha <mojha@codeaurora.org>
Cheers,
-Mukesh
> ---
> drivers/watchdog/intel_scu_watchdog.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/watchdog/intel_scu_watchdog.c b/drivers/watchdog/intel_scu_watchdog.c
> index 0caab6241eb7..718f7db35bec 100644
> --- a/drivers/watchdog/intel_scu_watchdog.c
> +++ b/drivers/watchdog/intel_scu_watchdog.c
> @@ -224,7 +224,7 @@ static int intel_scu_set_heartbeat(u32 t)
> watchdog_device.timer_tbl_ptr->freq_hz);
> pr_debug("set_heartbeat: timer_set is %x (hex)\n",
> watchdog_device.timer_set);
> - pr_debug("set_hearbeat: timer_margin is %x (hex)\n", timer_margin);
> + pr_debug("set_heartbeat: timer_margin is %x (hex)\n", timer_margin);
> pr_debug("set_heartbeat: threshold is %x (hex)\n",
> watchdog_device.threshold);
> pr_debug("set_heartbeat: soft_threshold is %x (hex)\n",
prev parent reply other threads:[~2019-04-17 6:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 13:33 [PATCH] watchdog: intel_scu_watchdog: fix spelling mistake: "set_hearbeat" -> "set_heartbeat" Colin King
2019-04-16 13:36 ` Guenter Roeck
2019-04-17 6:31 ` Mukesh Ojha [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=8149cea7-d7dd-2907-3f85-caba792b7cf0@codeaurora.org \
--to=mojha@codeaurora.org \
--cc=colin.king@canonical.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).