From: Randy Dunlap <rdunlap@infradead.org>
To: Seth Jennings <sjenning@linux.vnet.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, trivial@kernel.org
Subject: Re: [PATCH] mm: trivial: fix typos
Date: Fri, 11 Oct 2013 18:19:33 -0700 [thread overview]
Message-ID: <5258A3A5.8080700@infradead.org> (raw)
In-Reply-To: <1381163029-8808-1-git-send-email-sjenning@linux.vnet.ibm.com>
On 10/07/13 09:23, Seth Jennings wrote:
> Fix comment typos in swapfile.c
>
> Signed-off-by: Seth Jennings <sjenning@linux.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
prev parent reply other threads:[~2013-10-12 1:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-07 16:23 Seth Jennings
2013-10-12 1:19 ` Randy Dunlap [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=5258A3A5.8080700@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sjenning@linux.vnet.ibm.com \
--cc=trivial@kernel.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
all inboxes | Powered by JetHome®