From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Minchan Kim <minchan@kernel.org>
Cc: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Xishi Qiu <qiuxishi@huawei.com>,
ngupta@vflare.org, Linux MM <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: mm: fix typo of cache_alloc_zspage()
Date: Thu, 29 Dec 2016 17:03:51 +0900 [thread overview]
Message-ID: <20161229080351.GC3892@jagdpanzerIV.localdomain> (raw)
In-Reply-To: <20161229075654.GF1815@bbox>
On (12/29/16 16:56), Minchan Kim wrote:
> > for instance, we can have Xishi's fix up as part of this "fix documentation
> > typos" patch. which can be counted in as trivial.
>
> Xishi, Could you send your patch with fixing ones Sergey pointed out
> if Sergey doesn't mind?
I don't.
Reviewed-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
will be more than enough (well, to me).
> > - * A single 'zspage' is composed of up to 2^N discontiguous 0-order (single)
> > + * A single 'zspage' is composed of up to 2^N discontinuous 0-order (single)
>
> Hmm, discontinuous is right?
> I'm not a native but discontiguos is wrong? "contiguous" was used mm part widely.
oh, you're definitely much closer to native speaker than `aspell' tool!
you're right. Xishi, please drop that 'discontiguous' "correction".
sorry for that.
-ss
next prev parent reply other threads:[~2016-12-29 8:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-29 2:06 mm: fix typo of cache_alloc_zspage() Xishi Qiu
2016-12-29 6:44 ` Minchan Kim
2016-12-29 6:52 ` Sergey Senozhatsky
2016-12-29 6:59 ` Minchan Kim
2016-12-29 7:34 ` Sergey Senozhatsky
2016-12-29 7:56 ` Minchan Kim
2016-12-29 8:03 ` Sergey Senozhatsky [this message]
2016-12-29 10:34 ` Xishi Qiu
2016-12-30 1:07 ` Sergey Senozhatsky
2016-12-29 7:54 ` [PATCH V2] " Xishi Qiu
2017-01-06 4:08 ` [PATCH] mm: fix some typos in mm/zsmalloc.c Xishi Qiu
2017-01-06 4:38 ` Minchan Kim
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=20161229080351.GC3892@jagdpanzerIV.localdomain \
--to=sergey.senozhatsky.work@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.org \
--cc=qiuxishi@huawei.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).