All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu@kernel.org>
To: Yang Yingliang <yangyingliang@huawei.com>
Cc: linux-mm@kvack.org, shradhagupta@linux.microsoft.com,
	mikelley@microsoft.com, akpm@linux-foundation.org,
	wei.liu@kernel.org
Subject: Re: [PATCH -next] mm/page_reporting: change page_reporting_param_ops to static
Date: Wed, 2 Nov 2022 15:48:57 +0000	[thread overview]
Message-ID: <Y2KRaUAMgcbPrKi6@liuwe-devbox-debian-v2> (raw)
In-Reply-To: <20221101070022.1930028-1-yangyingliang@huawei.com>

On Tue, Nov 01, 2022 at 03:00:22PM +0800, Yang Yingliang wrote:
> page_reporting_param_ops is only used in page_reporting.c now,
> change it to static.
> 
> Fixes: 443063e483e3 ("mm/page_reporting: Add checks for page_reporting_order param")
> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>

This is already fixed in hyperv-next. Thanks.

> ---
>  mm/page_reporting.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/mm/page_reporting.c b/mm/page_reporting.c
> index 29d67c824fd2..6a8cb3b1ae1b 100644
> --- a/mm/page_reporting.c
> +++ b/mm/page_reporting.c
> @@ -23,7 +23,7 @@ int page_order_update_notify(const char *val, const struct kernel_param *kp)
>  	return  param_set_uint_minmax(val, kp, 0, MAX_ORDER-1);
>  }
>  
> -const struct kernel_param_ops page_reporting_param_ops = {
> +static const struct kernel_param_ops page_reporting_param_ops = {
>  	.set = &page_order_update_notify,
>  	/*
>  	 * For the get op, use param_get_int instead of param_get_uint.
> -- 
> 2.25.1
> 


      reply	other threads:[~2022-11-02 15:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-01  7:00 [PATCH -next] mm/page_reporting: change page_reporting_param_ops to static Yang Yingliang
2022-11-02 15:48 ` Wei Liu [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=Y2KRaUAMgcbPrKi6@liuwe-devbox-debian-v2 \
    --to=wei.liu@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-mm@kvack.org \
    --cc=mikelley@microsoft.com \
    --cc=shradhagupta@linux.microsoft.com \
    --cc=yangyingliang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.