Re: [PATCH] mm: remove unnecessary description about a non-exist gfp flag
From: Michal Hocko
Date: Wed Feb 17 2016 - 04:31:05 EST
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@xxxxxxxxxxxxxx>
Acked-by: Michal Hocko <mhocko@xxxxxxxx>
> ---
> 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@xxxxxxxxxx For more info on Linux MM,
> see: http://www.linux-mm.org/ .
> Don't email: <a href=mailto:"dont@xxxxxxxxx"> email@xxxxxxxxx </a>
--
Michal Hocko
SUSE Labs