From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Semen Zhydenko <semen.zhydenko@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fixed typo in comments
Date: Tue, 17 Jan 2023 10:23:42 +0700 [thread overview]
Message-ID: <Y8YUvsLVZZvGZo3T@debian.me> (raw)
In-Reply-To: <20230116222254.74479-1-semen.zhydenko@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 993 bytes --]
On Mon, Jan 16, 2023 at 11:22:54PM +0100, Semen Zhydenko wrote:
> diff --git a/kernel/time/timer.c b/kernel/time/timer.c
> index 63a8ce7177dd..6430c00b05a9 100644
> --- a/kernel/time/timer.c
> +++ b/kernel/time/timer.c
> @@ -1324,7 +1324,7 @@ static int __timer_delete(struct timer_list *timer, bool shutdown)
> * If @shutdown is set then the lock has to be taken whether the
> * timer is pending or not to protect against a concurrent rearm
> * which might hit between the lockless pending check and the lock
> - * aquisition. By taking the lock it is ensured that such a newly
> + * acquisition. By taking the lock it is ensured that such a newly
> * enqueued timer is dequeued and cannot end up with
> * timer->function == NULL in the expiry code.
> *
No patch description, really?
Also please read Documentation/process/submitting-patches.rst for how to
properly submit kernel patches.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-01-17 3:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 22:22 [PATCH] Fixed typo in comments Semen Zhydenko
2023-01-17 3:23 ` Bagas Sanjaya [this message]
[not found] ` <CACbEQFHP90RYNEBGP5jvPNVYciuiUwA7G0Gp9_8KAKc4-hgUTA@mail.gmail.com>
2023-01-18 2:12 ` Bagas Sanjaya
2023-01-18 22:08 ` Semen Zhydenko
2023-01-19 2:20 ` Bagas Sanjaya
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=Y8YUvsLVZZvGZo3T@debian.me \
--to=bagasdotme@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=semen.zhydenko@gmail.com \
/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