linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: <Conor.Dooley@microchip.com>
To: <lkp@intel.com>, <jaswinder.singh@linaro.org>
Cc: <kbuild-all@lists.01.org>, <clang-built-linux@googlegroups.com>,
	<linux-mm@kvack.org>
Subject: Re: [linux-next:master 10881/13550] include/soc/microchip/mpfs.h:49:29: warning: no previous prototype for function 'mpfs_sys_controller_get'
Date: Fri, 25 Jun 2021 14:17:23 +0000	[thread overview]
Message-ID: <f6637f16-a8d5-db1f-5c4c-29b88ce020b4@microchip.com> (raw)
In-Reply-To: <202106252019.HwE1jcxX-lkp@intel.com>

On 25/06/2021 13:48, kernel test robot wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> Hi Conor,
>
> FYI, the error/warning still remains.
Hi,
I resubmitted my series since to fix these errors and another, plus a 
fix in another file.
I believe i forgot to add the reported by tags, should I resend with the 
appropriate tags added?
Conor.
>
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head:   8702f95941c215501826ea8743a8b64b83479209
> commit: de5473936808627fa98c3d2e8e3fa3076338f601 [10881/13550] mbox: add polarfire soc system controller mailbox
> config: x86_64-randconfig-r015-20210625 (attached as .config)
> compiler: clang version 13.0.0 (https://github.com/llvm/llvm-project 9ca0171a9ffdef5fdb1511d197a3fd72490362de)
> reproduce (this is a W=1 build):
>          wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
>          chmod +x ~/bin/make.cross
>          # install x86_64 cross compiling tool for clang build
>          # apt-get install binutils-x86-64-linux-gnu
>          # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=de5473936808627fa98c3d2e8e3fa3076338f601
>          git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
>          git fetch --no-tags linux-next master
>          git checkout de5473936808627fa98c3d2e8e3fa3076338f601
>          # save the attached .config to linux build tree
>          COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=x86_64
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
>
> All warnings (new ones prefixed by >>):
>
>     In file included from drivers/mailbox/mailbox-mpfs.c:19:
>>> include/soc/microchip/mpfs.h:49:29: warning: no previous prototype for function 'mpfs_sys_controller_get' [-Wmissing-prototypes]
>     struct mpfs_sys_controller *mpfs_sys_controller_get(struct device_node *mailbox_node)
>                                 ^
>     include/soc/microchip/mpfs.h:49:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
>     struct mpfs_sys_controller *mpfs_sys_controller_get(struct device_node *mailbox_node)
>     ^
>     static
>     include/soc/microchip/mpfs.h:43:12: warning: unused function 'mpfs_blocking_transaction' [-Wunused-function]
>     static int mpfs_blocking_transaction(struct mpfs_sys_controller *mpfs_client, void *msg,
>                ^
>     2 warnings generated.
>
>
> vim +/mpfs_sys_controller_get +49 include/soc/microchip/mpfs.h
>
>      48
>    > 49  struct mpfs_sys_controller *mpfs_sys_controller_get(struct device_node *mailbox_node)
>      50  {
>      51          return NULL;
>      52  }
>      53
>
> ---
> 0-DAY CI Kernel Test Service, Intel Corporation
> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org




      reply	other threads:[~2021-06-25 14:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-25 12:48 kernel test robot
2021-06-25 14:17 ` Conor.Dooley [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=f6637f16-a8d5-db1f-5c4c-29b88ce020b4@microchip.com \
    --to=conor.dooley@microchip.com \
    --cc=clang-built-linux@googlegroups.com \
    --cc=jaswinder.singh@linaro.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.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