linux-trace-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: "wuqiang.matt" <wuqiang.matt@bytedance.com>
Cc: linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org,
	lkp@intel.com, mattwu@163.com
Subject: Re: [PATCH v1] lib: test_objpool: make global variables static
Date: Wed, 8 Nov 2023 12:11:23 +0900	[thread overview]
Message-ID: <20231108121123.881efce0a736a3e98f6e99d6@kernel.org> (raw)
In-Reply-To: <20231108012248.313574-1-wuqiang.matt@bytedance.com>

On Wed,  8 Nov 2023 09:22:48 +0800
"wuqiang.matt" <wuqiang.matt@bytedance.com> wrote:

> Kernel test robot reported build warnings that structures g_ot_sync_ops,
> g_ot_async_ops and g_testcases should be static. These definitions are
> only used in test_objpool.c, so make them static
> 
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202311071229.WGrWUjM1-lkp@intel.com/
> 

Looks good to me.

Acked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>

Let me pick this to probes/fixes.

Thank you,

> Signed-off-by: wuqiang.matt <wuqiang.matt@bytedance.com>
> ---
>  lib/test_objpool.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/lib/test_objpool.c b/lib/test_objpool.c
> index a94078402138..bfdb81599832 100644
> --- a/lib/test_objpool.c
> +++ b/lib/test_objpool.c
> @@ -311,7 +311,7 @@ static void ot_fini_sync(struct ot_context *sop)
>  	ot_kfree(sop->test, sop, sizeof(*sop));
>  }
>  
> -struct {
> +static struct {
>  	struct ot_context * (*init)(struct ot_test *oc);
>  	void (*fini)(struct ot_context *sop);
>  } g_ot_sync_ops[] = {
> @@ -475,7 +475,7 @@ static struct ot_context *ot_init_async_m0(struct ot_test *test)
>  	return sop;
>  }
>  
> -struct {
> +static struct {
>  	struct ot_context * (*init)(struct ot_test *oc);
>  	void (*fini)(struct ot_context *sop);
>  } g_ot_async_ops[] = {
> @@ -632,7 +632,7 @@ static int ot_start_async(struct ot_test *test)
>  #define NODE_COMPACT sizeof(struct ot_node)
>  #define NODE_VMALLOC (512)
>  
> -struct ot_test g_testcases[] = {
> +static struct ot_test g_testcases[] = {
>  
>  	/* sync & normal */
>  	{0, 0, NODE_COMPACT, 1000, 0,  1,  0,  0, "sync: percpu objpool"},
> -- 
> 2.40.1
> 


-- 
Masami Hiramatsu (Google) <mhiramat@kernel.org>

      reply	other threads:[~2023-11-08  3:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-08  1:22 [PATCH v1] lib: test_objpool: make global variables static wuqiang.matt
2023-11-08  3:11 ` Masami Hiramatsu [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=20231108121123.881efce0a736a3e98f6e99d6@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mattwu@163.com \
    --cc=wuqiang.matt@bytedance.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).