From: Michal Hocko <mhocko@kernel.org>
To: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
Cc: linux-kernel@vger.kernel.org, linux-mm <linux-mm@kvack.org>
Subject: Re: [PATCH] mm: remove unnecessary description about a non-exist gfp flag
Date: Wed, 17 Feb 2016 10:30:55 +0100 [thread overview]
Message-ID: <20160217093054.GA29196@dhcp22.suse.cz> (raw)
In-Reply-To: <56C411A3.6090208@jp.fujitsu.com>
On Wed 17-02-16 15:22:27, Satoru Takeuchi wrote:
> Since __GFP_NOACCOUNT is removed by the following commit,
> its description is not necessary.
>
> commit 20b5c3039863 ("Revert 'gfp: add __GFP_NOACCOUNT'")
>
> Signed-off-by: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
Acked-by: Michal Hocko <mhocko@suse.com>
> ---
> include/linux/gfp.h | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/include/linux/gfp.h b/include/linux/gfp.h
> index af1f2b2..7c76a6e 100644
> --- a/include/linux/gfp.h
> +++ b/include/linux/gfp.h
> @@ -101,8 +101,6 @@ struct vm_area_struct;
> *
> * __GFP_NOMEMALLOC is used to explicitly forbid access to emergency reserves.
> * This takes precedence over the __GFP_MEMALLOC flag if both are set.
> - *
> - * __GFP_NOACCOUNT ignores the accounting for kmemcg limit enforcement.
> */
> #define __GFP_ATOMIC ((__force gfp_t)___GFP_ATOMIC)
> #define __GFP_HIGH ((__force gfp_t)___GFP_HIGH)
> --
> 2.5.0
>
> --
> To unsubscribe, send a message with 'unsubscribe linux-mm' in
> the body to majordomo@kvack.org. For more info on Linux MM,
> see: http://www.linux-mm.org/ .
> Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
--
Michal Hocko
SUSE Labs
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2016-02-17 9:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 6:22 Satoru Takeuchi
2016-02-17 9:30 ` Michal Hocko [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=20160217093054.GA29196@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=takeuchi_satoru@jp.fujitsu.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