From: "tip-bot2 for Mukesh Ojha" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Mukesh Ojha <mojha@codeaurora.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>, Borislav Petkov <bp@alien8.de>,
linux-kernel@vger.kernel.org
Subject: [tip: timers/core] time: Fix spelling mistake in comment
Date: Tue, 12 Nov 2019 10:32:40 -0000 [thread overview]
Message-ID: <157355476063.29376.3227779653988744811.tip-bot2@tip-bot2> (raw)
In-Reply-To: <1571124819-9639-1-git-send-email-mojha@codeaurora.org>
The following commit has been merged into the timers/core branch of tip:
Commit-ID: 1d6acc18fee71a0db6e4fbbfbdb247e0bd5b0655
Gitweb: https://git.kernel.org/tip/1d6acc18fee71a0db6e4fbbfbdb247e0bd5b0655
Author: Mukesh Ojha <mojha@codeaurora.org>
AuthorDate: Tue, 15 Oct 2019 13:03:39 +05:30
Committer: Thomas Gleixner <tglx@linutronix.de>
CommitterDate: Tue, 12 Nov 2019 11:30:46 +01:00
time: Fix spelling mistake in comment
witin => within
Signed-off-by: Mukesh Ojha <mojha@codeaurora.org>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Link: https://lkml.kernel.org/r/1571124819-9639-1-git-send-email-mojha@codeaurora.org
---
kernel/time/time.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/time/time.c b/kernel/time/time.c
index 45a3589..ea6e7e4 100644
--- a/kernel/time/time.c
+++ b/kernel/time/time.c
@@ -179,7 +179,7 @@ int do_sys_settimeofday64(const struct timespec64 *tv, const struct timezone *tz
return error;
if (tz) {
- /* Verify we're witin the +-15 hrs range */
+ /* Verify we're within the +-15 hrs range */
if (tz->tz_minuteswest > 15*60 || tz->tz_minuteswest < -15*60)
return -EINVAL;
prev parent reply other threads:[~2019-11-12 10:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-15 7:33 [PATCH 2/3] time: Fix spelling mistake in comment Mukesh Ojha
2019-11-12 10:32 ` tip-bot2 for 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=157355476063.29376.3227779653988744811.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mojha@codeaurora.org \
--cc=tglx@linutronix.de \
/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).