linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, rdunlap@infradead.org
Subject: Re: [PATCH] mm: Typo fix in the file util.c
Date: Wed, 17 Mar 2021 11:48:10 +0000	[thread overview]
Message-ID: <20210317114810.GF3420@casper.infradead.org> (raw)
In-Reply-To: <20210317033439.3429411-1-unixbhaskar@gmail.com>

On Wed, Mar 17, 2021 at 09:04:39AM +0530, Bhaskar Chowdhury wrote:
> 
> 
> s/condtion/condition/

The usual subject line for this would be:

mm/util: Fix typo

> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
> ---
>  mm/util.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/mm/util.c b/mm/util.c
> index 54870226cea6..f85da35b50eb 100644
> --- a/mm/util.c
> +++ b/mm/util.c
> @@ -775,7 +775,7 @@ int overcommit_policy_handler(struct ctl_table *table, int write, void *buffer,
>  	 * The deviation of sync_overcommit_as could be big with loose policy
>  	 * like OVERCOMMIT_ALWAYS/OVERCOMMIT_GUESS. When changing policy to
>  	 * strict OVERCOMMIT_NEVER, we need to reduce the deviation to comply
> -	 * with the strict "NEVER", and to avoid possible race condtion (even
> +	 * with the strict "NEVER", and to avoid possible race condition (even
>  	 * though user usually won't too frequently do the switching to policy
>  	 * OVERCOMMIT_NEVER), the switch is done in the following order:
>  	 *	1. changing the batch
> --
> 2.30.2
> 
> 

  parent reply	other threads:[~2021-03-17 11:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-17  3:34 [PATCH] mm: Typo fix in the file util.c Bhaskar Chowdhury
2021-03-17  5:15 ` Randy Dunlap
2021-03-17 11:48 ` Matthew Wilcox [this message]
2021-03-17 22:45   ` Bhaskar Chowdhury

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=20210317114810.GF3420@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=rdunlap@infradead.org \
    --cc=unixbhaskar@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;
as well as URLs for NNTP newsgroup(s).