linux-kernel - Re: [PATCH] mm: trivial: fix typos

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <5258A3A5.8080700@infradead.org>
Date:	Fri, 11 Oct 2013 18:19:33 -0700
From:	Randy Dunlap <rdunlap@...radead.org>
To:	Seth Jennings <sjenning@...ux.vnet.ibm.com>,
	Andrew Morton <akpm@...ux-foundation.org>
CC:	linux-kernel@...r.kernel.org, trivial@...nel.org
Subject: Re: [PATCH] mm: trivial: fix typos

On 10/07/13 09:23, Seth Jennings wrote:
> Fix comment typos in swapfile.c
> 
> Signed-off-by: Seth Jennings <sjenning@...ux.vnet.ibm.com>
> ---
>  mm/swapfile.c | 14 +++++++-------
>  1 file changed, 7 insertions(+), 7 deletions(-)
> 
> diff --git a/mm/swapfile.c b/mm/swapfile.c
> index 3963fc2..7968c1b 100644
> --- a/mm/swapfile.c
> +++ b/mm/swapfile.c
> @@ -1179,7 +1179,7 @@ static int unuse_pte_range(struct vm_area_struct *vma, pmd_t *pmd,
>  	 * some architectures (e.g. x86_32 with PAE) we might catch a glimpse
>  	 * of unmatched parts which look like swp_pte, so unuse_pte must
>  	 * recheck under pte lock.  Scanning without pte lock lets it be
> -	 * preemptible whenever CONFIG_PREEMPT but not CONFIG_HIGHPTE.
> +	 * preemptable whenever CONFIG_PREEMPT but not CONFIG_HIGHPTE.

Do you have a dictionary source that backs this one up?

The kernel source uses either spelling.

dict.org doesn't find either spelling.
m-w.com doesn't find either spelling.
However, dictionary.com finds preemptible but not preemptable.


>  	 */
>  	pte = pte_offset_map(pmd, addr);
>  	do {



-- 
~Randy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/