All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: npiggin@gmail.com, benh@kernel.crashing.org, mpe@ellerman.id.au,
	alistair@popple.id.au, maddy@linux.ibm.com,
	christophe.leroy@csgroup.eu, ravi.bangoria@linux.ibm.com,
	rppt@kernel.org, paulus@samba.org, john.ogness@linutronix.de,
	jniethe5@gmail.com, pmladek@suse.com,
	Pu Lehui <pulehui@huawei.com>
Cc: yangjihong1@huawei.com, zhangjinhao2@huawei.com,
	linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] powerpc/xmon: Make symbol 'spu_inst_dump' static
Date: Mon, 19 Apr 2021 13:59:58 +1000	[thread overview]
Message-ID: <161880479868.1398509.405544111450941367.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20210409070151.163424-1-pulehui@huawei.com>

On Fri, 9 Apr 2021 15:01:51 +0800, Pu Lehui wrote:
> Fix sparse warning:
> 
> arch/powerpc/xmon/xmon.c:4216:1: warning:
>  symbol 'spu_inst_dump' was not declared. Should it be static?
> 
> This symbol is not used outside of xmon.c, so make it static.

Applied to powerpc/next.

[1/1] powerpc/xmon: Make symbol 'spu_inst_dump' static
      https://git.kernel.org/powerpc/c/f234ad405a35262ed2d8dd2d29fc633908dce955

cheers

WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: npiggin@gmail.com, benh@kernel.crashing.org, mpe@ellerman.id.au,
	alistair@popple.id.au, maddy@linux.ibm.com,
	christophe.leroy@csgroup.eu, ravi.bangoria@linux.ibm.com,
	rppt@kernel.org, paulus@samba.org, john.ogness@linutronix.de,
	jniethe5@gmail.com, pmladek@suse.com,
	Pu Lehui <pulehui@huawei.com>
Cc: zhangjinhao2@huawei.com, yangjihong1@huawei.com,
	linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] powerpc/xmon: Make symbol 'spu_inst_dump' static
Date: Mon, 19 Apr 2021 13:59:58 +1000	[thread overview]
Message-ID: <161880479868.1398509.405544111450941367.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20210409070151.163424-1-pulehui@huawei.com>

On Fri, 9 Apr 2021 15:01:51 +0800, Pu Lehui wrote:
> Fix sparse warning:
> 
> arch/powerpc/xmon/xmon.c:4216:1: warning:
>  symbol 'spu_inst_dump' was not declared. Should it be static?
> 
> This symbol is not used outside of xmon.c, so make it static.

Applied to powerpc/next.

[1/1] powerpc/xmon: Make symbol 'spu_inst_dump' static
      https://git.kernel.org/powerpc/c/f234ad405a35262ed2d8dd2d29fc633908dce955

cheers

  reply	other threads:[~2021-04-19  4:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-09  7:01 [PATCH -next] powerpc/xmon: Make symbol 'spu_inst_dump' static Pu Lehui
2021-04-09  7:01 ` Pu Lehui
2021-04-19  3:59 ` Michael Ellerman [this message]
2021-04-19  3:59   ` Michael Ellerman

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=161880479868.1398509.405544111450941367.b4-ty@ellerman.id.au \
    --to=patch-notifications@ellerman.id.au \
    --cc=alistair@popple.id.au \
    --cc=benh@kernel.crashing.org \
    --cc=christophe.leroy@csgroup.eu \
    --cc=jniethe5@gmail.com \
    --cc=john.ogness@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.ibm.com \
    --cc=mpe@ellerman.id.au \
    --cc=npiggin@gmail.com \
    --cc=paulus@samba.org \
    --cc=pmladek@suse.com \
    --cc=pulehui@huawei.com \
    --cc=ravi.bangoria@linux.ibm.com \
    --cc=rppt@kernel.org \
    --cc=yangjihong1@huawei.com \
    --cc=zhangjinhao2@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.