linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fabio Estevam <festevam@gmail.com>
To: kernel test robot <lkp@intel.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>
Cc: kbuild-all@lists.01.org,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	linux-media <linux-media@vger.kernel.org>,
	Hans Verkuil <hverkuil@xs4all.nl>
Subject: Re: drivers/media/platform/fsl-viu.c:253:2: error: implicit declaration of function 'out_be32'
Date: Thu, 19 Nov 2020 20:11:12 -0300	[thread overview]
Message-ID: <CAOMZO5CJb_8AoaEPG67tVTV=dB3m7C+zX=Ka7mvPv2Xb4OF73g@mail.gmail.com> (raw)
In-Reply-To: <202011190936.brIiila6-lkp@intel.com>

On Wed, Nov 18, 2020 at 10:15 PM kernel test robot <lkp@intel.com> wrote:
>
> Hi Fabio,
>
> FYI, the error/warning still remains.
>
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head:   c2e7554e1b85935d962127efa3c2a76483b0b3b6
> commit: 17621758e53f0e6bf1ac469cca2a59fa6457d205 media: fsl-viu: Do not redefine out_be32()/in_be32() for CONFIG_M68K
> date:   3 months ago
> config: m68k-randconfig-r013-20201118 (attached as .config)
> compiler: m68k-linux-gcc (GCC) 9.3.0
> 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
>         # https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=17621758e53f0e6bf1ac469cca2a59fa6457d205
>         git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
>         git fetch --no-tags linus master
>         git checkout 17621758e53f0e6bf1ac469cca2a59fa6457d205
>         # save the attached .config to linux build tree
>         COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=m68k
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>):
>
>    drivers/media/platform/fsl-viu.c: In function 'viu_start_dma':
> >> drivers/media/platform/fsl-viu.c:253:2: error: implicit declaration of function 'out_be32' [-Werror=implicit-function-declaration]
>      253 |  out_be32(&vr->status_cfg, SOFT_RST);
>          |  ^~~~~~~~
>    drivers/media/platform/fsl-viu.c: In function 'viu_stop_dma':
> >> drivers/media/platform/fsl-viu.c:266:15: error: implicit declaration of function 'in_be32' [-Werror=implicit-function-declaration]
>      266 |  status_cfg = in_be32(&vr->status_cfg);
>          |               ^~~~~~~
>    cc1: some warnings being treated as errors

It seems that Geert has submitted a proper fix a long time ago:
https://lkml.org/lkml/2020/8/17/2376

  reply	other threads:[~2020-11-19 23:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-19  1:15 drivers/media/platform/fsl-viu.c:253:2: error: implicit declaration of function 'out_be32' kernel test robot
2020-11-19 23:11 ` Fabio Estevam [this message]
2020-11-20  4:52 kernel test robot

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='CAOMZO5CJb_8AoaEPG67tVTV=dB3m7C+zX=Ka7mvPv2Xb4OF73g@mail.gmail.com' \
    --to=festevam@gmail.com \
    --cc=geert@linux-m68k.org \
    --cc=hverkuil@xs4all.nl \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mchehab@kernel.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 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).