linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Wei Yang <richard.weiyang@gmail.com>
To: Hao Lee <haolee.swjtu@gmail.com>
Cc: akpm@linux-foundation.org, alexander.h.duyck@intel.com,
	mhocko@suse.com, vbabka@suse.cz, mgorman@suse.de,
	l.stach@pengutronix.de, vdavydov.dev@gmail.com,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: fix spelling error
Date: Wed, 10 May 2017 10:38:13 +0800	[thread overview]
Message-ID: <20170510023813.GA8480@WeideMBP.lan> (raw)
In-Reply-To: <20170403161655.5081-1-haolee.swjtu@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1151 bytes --]

On Tue, Apr 04, 2017 at 12:16:55AM +0800, Hao Lee wrote:
>Fix variable name error in comments. No code changes.
>
>Signed-off-by: Hao Lee <haolee.swjtu@gmail.com>
>---
> include/linux/gfp.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
>diff --git a/include/linux/gfp.h b/include/linux/gfp.h
>index db373b9..ff3d651 100644
>--- a/include/linux/gfp.h
>+++ b/include/linux/gfp.h
>@@ -297,8 +297,8 @@ static inline bool gfpflags_allow_blocking(const gfp_t gfp_flags)
> 
> /*
>  * GFP_ZONE_TABLE is a word size bitstring that is used for looking up the
>- * zone to use given the lowest 4 bits of gfp_t. Entries are ZONE_SHIFT long
>- * and there are 16 of them to cover all possible combinations of
>+ * zone to use given the lowest 4 bits of gfp_t. Entries are GFP_ZONES_SHIFT
>+ * bits long and there are 16 of them to cover all possible combinations of
>  * __GFP_DMA, __GFP_DMA32, __GFP_MOVABLE and __GFP_HIGHMEM.
>  *
>  * The zone fallback order is MOVABLE=>HIGHMEM=>NORMAL=>DMA32=>DMA.

Looks good to me.

Acked-by: Wei Yang <richard.weiyang@gmail.com>

>-- 
>2.9.3

-- 
Wei Yang
Help you, Help me

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2017-05-10  2:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-03 16:16 Hao Lee
2017-05-10  2:38 ` Wei Yang [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=20170510023813.GA8480@WeideMBP.lan \
    --to=richard.weiyang@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=alexander.h.duyck@intel.com \
    --cc=haolee.swjtu@gmail.com \
    --cc=l.stach@pengutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=mhocko@suse.com \
    --cc=vbabka@suse.cz \
    --cc=vdavydov.dev@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