public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: tumic@gpxsee.org, Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-media@vger.kernel.org,
	linux-kernel@vger.kernel.org, "Lizhi Hou" <lizhi.hou@amd.com>,
	"Martin Tůma" <martin.tuma@digiteqautomotive.com>
Subject: Re: [PATCH RESEND v5 1/1] Added Digiteq Automotive MGB4 driver
Date: Wed, 8 Feb 2023 04:42:33 +0800	[thread overview]
Message-ID: <202302080423.3mOPztPU-lkp@intel.com> (raw)
In-Reply-To: <20230207150119.5542-2-tumic@gpxsee.org>

Hi,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on sailus-media-tree/streams]
[also build test ERROR on linus/master v6.2-rc7]
[cannot apply to media-tree/master next-20230207]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/tumic-gpxsee-org/Added-Digiteq-Automotive-MGB4-driver/20230207-210120
base:   git://linuxtv.org/sailus/media_tree.git streams
patch link:    https://lore.kernel.org/r/20230207150119.5542-2-tumic%40gpxsee.org
patch subject: [PATCH RESEND v5 1/1] Added Digiteq Automotive MGB4 driver
config: s390-allyesconfig (https://download.01.org/0day-ci/archive/20230208/202302080423.3mOPztPU-lkp@intel.com/config)
compiler: s390-linux-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://github.com/intel-lab-lkp/linux/commit/ece664ba09047f289e8573fc17738d5eb29c265a
        git remote add linux-review https://github.com/intel-lab-lkp/linux
        git fetch --no-tags linux-review tumic-gpxsee-org/Added-Digiteq-Automotive-MGB4-driver/20230207-210120
        git checkout ece664ba09047f289e8573fc17738d5eb29c265a
        # 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=s390 olddefconfig
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=s390 SHELL=/bin/bash

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/media/pci/mgb4/mgb4_trigger.c:19:10: fatal error: linux/dma/amd_xdma.h: No such file or directory
      19 | #include <linux/dma/amd_xdma.h>
         |          ^~~~~~~~~~~~~~~~~~~~~~
   compilation terminated.
--
>> drivers/media/pci/mgb4/mgb4_core.c:29:10: fatal error: linux/dma/amd_xdma.h: No such file or directory
      29 | #include <linux/dma/amd_xdma.h>
         |          ^~~~~~~~~~~~~~~~~~~~~~
   compilation terminated.
--
>> drivers/media/pci/mgb4/mgb4_vin.c:24:10: fatal error: linux/dma/amd_xdma.h: No such file or directory
      24 | #include <linux/dma/amd_xdma.h>
         |          ^~~~~~~~~~~~~~~~~~~~~~
   compilation terminated.
--
>> drivers/media/pci/mgb4/mgb4_vout.c:17:10: fatal error: linux/dma/amd_xdma.h: No such file or directory
      17 | #include <linux/dma/amd_xdma.h>
         |          ^~~~~~~~~~~~~~~~~~~~~~
   compilation terminated.


vim +19 drivers/media/pci/mgb4/mgb4_trigger.c

  > 19	#include <linux/dma/amd_xdma.h>
    20	#include "mgb4_core.h"
    21	#include "mgb4_trigger.h"
    22	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests

      reply	other threads:[~2023-02-07 20:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-07 15:01 [PATCH RESEND v5 0/1] Digiteq Automotive MGB4 driver tumic
2023-02-07 15:01 ` [PATCH RESEND v5 1/1] Added " tumic
2023-02-07 20:42   ` kernel test robot [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=202302080423.3mOPztPU-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=lizhi.hou@amd.com \
    --cc=martin.tuma@digiteqautomotive.com \
    --cc=mchehab@kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=tumic@gpxsee.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