From: Heiko Carstens <hca@linux.ibm.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH linux-next] include/getcpu.h: Fixed kernel test robot warning
Date: Mon, 30 Nov 2020 14:18:48 +0100 [thread overview]
Message-ID: <20201130131848.GA11190@osiris> (raw)
In-Reply-To: <1606578117-2895-1-git-send-email-jrdr.linux@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1572 bytes --]
On Sat, Nov 28, 2020 at 09:11:57PM +0530, Souptick Joarder wrote:
> Kernel test robot generates below warning ->
>
> >> arch/s390/kernel/vdso64/getcpu.c:8:5: warning: no previous prototype
> >> for function '__s390_vdso_getcpu' [-Wmissing-prototypes]
> int __s390_vdso_getcpu(unsigned *cpu, unsigned *node, struct
> getcpu_cache *unused)
> ^
> arch/s390/kernel/vdso64/getcpu.c:8:1: note: declare 'static' if the
> function is not intended to be used outside of this translation unit
> int __s390_vdso_getcpu(unsigned *cpu, unsigned *node, struct
> getcpu_cache *unused)
> ^
> static
> 1 warning generated.
>
> vim +/__s390_vdso_getcpu +8 arch/s390/kernel/vdso64/getcpu.c
>
> 7
> > 8 int __s390_vdso_getcpu(unsigned *cpu, unsigned *node, struct
> > getcpu_cache *unused)
>
> It is fixed by adding a prototype.
>
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Souptick Joarder <jrdr.linux@gmail.com>
> ---
> include/linux/getcpu.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/include/linux/getcpu.h b/include/linux/getcpu.h
> index c304dcd..43c9208 100644
> --- a/include/linux/getcpu.h
> +++ b/include/linux/getcpu.h
> @@ -16,4 +16,5 @@ struct getcpu_cache {
> unsigned long blob[128 / sizeof(long)];
> };
>
> +int __s390_vdso_getcpu(unsigned *cpu, unsigned *node, struct getcpu_cache *unused);
Sorry, no. We won't add s390 specific prototypes to common code header
files. Anyway, I solved this differently and the "fix" should be in
linux-next soon.
WARNING: multiple messages have this Message-ID (diff)
From: Heiko Carstens <hca@linux.ibm.com>
To: Souptick Joarder <jrdr.linux@gmail.com>
Cc: kbuild-all@lists.01.org, svens@linux.ibm.com,
clang-built-linux@googlegroups.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH linux-next] include/getcpu.h: Fixed kernel test robot warning
Date: Mon, 30 Nov 2020 14:18:48 +0100 [thread overview]
Message-ID: <20201130131848.GA11190@osiris> (raw)
In-Reply-To: <1606578117-2895-1-git-send-email-jrdr.linux@gmail.com>
On Sat, Nov 28, 2020 at 09:11:57PM +0530, Souptick Joarder wrote:
> Kernel test robot generates below warning ->
>
> >> arch/s390/kernel/vdso64/getcpu.c:8:5: warning: no previous prototype
> >> for function '__s390_vdso_getcpu' [-Wmissing-prototypes]
> int __s390_vdso_getcpu(unsigned *cpu, unsigned *node, struct
> getcpu_cache *unused)
> ^
> arch/s390/kernel/vdso64/getcpu.c:8:1: note: declare 'static' if the
> function is not intended to be used outside of this translation unit
> int __s390_vdso_getcpu(unsigned *cpu, unsigned *node, struct
> getcpu_cache *unused)
> ^
> static
> 1 warning generated.
>
> vim +/__s390_vdso_getcpu +8 arch/s390/kernel/vdso64/getcpu.c
>
> 7
> > 8 int __s390_vdso_getcpu(unsigned *cpu, unsigned *node, struct
> > getcpu_cache *unused)
>
> It is fixed by adding a prototype.
>
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Souptick Joarder <jrdr.linux@gmail.com>
> ---
> include/linux/getcpu.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/include/linux/getcpu.h b/include/linux/getcpu.h
> index c304dcd..43c9208 100644
> --- a/include/linux/getcpu.h
> +++ b/include/linux/getcpu.h
> @@ -16,4 +16,5 @@ struct getcpu_cache {
> unsigned long blob[128 / sizeof(long)];
> };
>
> +int __s390_vdso_getcpu(unsigned *cpu, unsigned *node, struct getcpu_cache *unused);
Sorry, no. We won't add s390 specific prototypes to common code header
files. Anyway, I solved this differently and the "fix" should be in
linux-next soon.
next prev parent reply other threads:[~2020-11-30 13:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-28 15:41 [PATCH linux-next] include/getcpu.h: Fixed kernel test robot warning Souptick Joarder
2020-11-28 15:41 ` Souptick Joarder
2020-11-30 13:18 ` Heiko Carstens [this message]
2020-11-30 13:18 ` Heiko Carstens
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=20201130131848.GA11190@osiris \
--to=hca@linux.ibm.com \
--cc=kbuild-all@lists.01.org \
/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.