public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <treding@nvidia.com>
To: kernel test robot <lkp@intel.com>
Cc: Mikko Perttunen <mperttunen@nvidia.com>,
	kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: Re: drivers/gpu/host1x/context.c:65:23: error: too many arguments to function 'of_dma_configure_id'
Date: Wed, 24 Aug 2022 17:34:44 +0200	[thread overview]
Message-ID: <YwZFFFCD/LPDZn29@orome> (raw)
In-Reply-To: <202208240444.uTBVAbiI-lkp@intel.com>

[-- Attachment #1: Type: text/plain, Size: 2328 bytes --]

On Wed, Aug 24, 2022 at 04:59:56AM +0800, kernel test robot wrote:
> Hi Mikko,
> 
> FYI, the error/warning still remains.
> 
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head:   072e51356cd5a4a1c12c1020bc054c99b98333df
> commit: 8aa5bcb61612060429223d1fbb7a1c30a579fc1f gpu: host1x: Add context device management code
> date:   7 weeks ago
> config: arm-randconfig-r012-20220823 (https://download.01.org/0day-ci/archive/20220824/202208240444.uTBVAbiI-lkp@intel.com/config)
> compiler: arm-linux-gnueabi-gcc (GCC) 12.1.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=8aa5bcb61612060429223d1fbb7a1c30a579fc1f
>         git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
>         git fetch --no-tags linus master
>         git checkout 8aa5bcb61612060429223d1fbb7a1c30a579fc1f
>         # save the config file
>         mkdir build_dir && cp config build_dir/.config
>         COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=arm SHELL=/bin/bash drivers/gpu/host1x/
> 
> If you fix the issue, kindly add following tag where applicable
> Reported-by: kernel test robot <lkp@intel.com>
> 
> All errors (new ones prefixed by >>):
> 
>    drivers/gpu/host1x/context.c: In function 'host1x_memory_context_list_init':
> >> drivers/gpu/host1x/context.c:65:23: error: too many arguments to function 'of_dma_configure_id'
>       65 |                 err = of_dma_configure_id(&ctx->dev, node, true, &i);
>          |                       ^~~~~~~~~~~~~~~~~~~
>    In file included from include/linux/of_platform.h:12,
>                     from drivers/gpu/host1x/context.c:9:
>    include/linux/of_device.h:103:19: note: declared here
>      103 | static inline int of_dma_configure_id(struct device *dev,
>          |                   ^~~~~~~~~~~~~~~~~~~

Looks like this was caused by a mismatch in the signature of this
function for !OF builds. I've sent out a patch, so hopefully this will
get fixed in linux-next (and mainline) soon.

Thanks,
Thierry

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2022-08-24 15:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-23 20:59 drivers/gpu/host1x/context.c:65:23: error: too many arguments to function 'of_dma_configure_id' kernel test robot
2022-08-24 15:34 ` Thierry Reding [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=YwZFFFCD/LPDZn29@orome \
    --to=treding@nvidia.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mperttunen@nvidia.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