All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: oushixiong <oushixiong@kylinos.cn>, Dave Airlie <airlied@redhat.com>
Cc: oushixiong <oushixiong@kylinos.cn>,
	kbuild-all@lists.01.org, Thomas Zimmermann <tzimmermann@suse.de>,
	David Airlie <airlied@linux.ie>,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/ast: radeon amdgpu for ast add prime
Date: Fri, 12 Aug 2022 03:39:13 +0800	[thread overview]
Message-ID: <202208120345.REoTpw1K-lkp@intel.com> (raw)
In-Reply-To: <20220809114439.2063863-1-oushixiong@kylinos.cn>

Hi oushixiong,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on drm/drm-next]
[also build test WARNING on drm-intel/for-linux-next linus/master v5.19 next-20220811]
[cannot apply to drm-misc/drm-misc-next drm-tip/drm-tip]
[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/oushixiong/drm-ast-radeon-amdgpu-for-ast-add-prime/20220811-115710
base:   git://anongit.freedesktop.org/drm/drm drm-next
config: i386-randconfig-s002 (https://download.01.org/0day-ci/archive/20220812/202208120345.REoTpw1K-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-3) 11.3.0
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.4-39-gce1a6720-dirty
        # https://github.com/intel-lab-lkp/linux/commit/1b9b79a00132f2917ca66bea714a6f21fc939b0f
        git remote add linux-review https://github.com/intel-lab-lkp/linux
        git fetch --no-tags linux-review oushixiong/drm-ast-radeon-amdgpu-for-ast-add-prime/20220811-115710
        git checkout 1b9b79a00132f2917ca66bea714a6f21fc939b0f
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=i386 SHELL=/bin/bash drivers/gpu/drm/ast/

If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>

sparse warnings: (new ones prefixed by >>)
   drivers/gpu/drm/ast/ast_drv.c:43:5: sparse: sparse: symbol 'ast_modeset' was not declared. Should it be static?
>> drivers/gpu/drm/ast/ast_drv.c:54:23: sparse: sparse: symbol 'ast_gem_prime_import_sg_table' was not declared. Should it be static?
--
   drivers/gpu/drm/ast/ast_mode.c:681:19: sparse: sparse: cast removes address space '__iomem' of expression
   drivers/gpu/drm/ast/ast_mode.c:681:16: sparse: sparse: incorrect type in assignment (different address spaces) @@     expected unsigned char [noderef] [usertype] __iomem *dstxor @@     got unsigned char [usertype] * @@
   drivers/gpu/drm/ast/ast_mode.c:681:16: sparse:     expected unsigned char [noderef] [usertype] __iomem *dstxor
   drivers/gpu/drm/ast/ast_mode.c:681:16: sparse:     got unsigned char [usertype] *
>> drivers/gpu/drm/ast/ast_mode.c:1759:33: sparse: sparse: incorrect type in argument 1 (different address spaces) @@     expected void volatile [noderef] __iomem * @@     got void * @@
   drivers/gpu/drm/ast/ast_mode.c:1759:33: sparse:     expected void volatile [noderef] __iomem *
   drivers/gpu/drm/ast/ast_mode.c:1759:33: sparse:     got void *
>> drivers/gpu/drm/ast/ast_mode.c:1713:5: sparse: sparse: symbol 'ast_handle_damage' was not declared. Should it be static?
>> drivers/gpu/drm/ast/ast_mode.c:1814:24: sparse: sparse: symbol 'ast_gem_fb_create_with_dirty' was not declared. Should it be static?

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp

WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: oushixiong <oushixiong@kylinos.cn>, Dave Airlie <airlied@redhat.com>
Cc: kbuild-all@lists.01.org, Thomas Zimmermann <tzimmermann@suse.de>,
	David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	oushixiong <oushixiong@kylinos.cn>
Subject: Re: [PATCH] drm/ast: radeon amdgpu for ast add prime
Date: Fri, 12 Aug 2022 03:39:13 +0800	[thread overview]
Message-ID: <202208120345.REoTpw1K-lkp@intel.com> (raw)
In-Reply-To: <20220809114439.2063863-1-oushixiong@kylinos.cn>

Hi oushixiong,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on drm/drm-next]
[also build test WARNING on drm-intel/for-linux-next linus/master v5.19 next-20220811]
[cannot apply to drm-misc/drm-misc-next drm-tip/drm-tip]
[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/oushixiong/drm-ast-radeon-amdgpu-for-ast-add-prime/20220811-115710
base:   git://anongit.freedesktop.org/drm/drm drm-next
config: i386-randconfig-s002 (https://download.01.org/0day-ci/archive/20220812/202208120345.REoTpw1K-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-3) 11.3.0
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.4-39-gce1a6720-dirty
        # https://github.com/intel-lab-lkp/linux/commit/1b9b79a00132f2917ca66bea714a6f21fc939b0f
        git remote add linux-review https://github.com/intel-lab-lkp/linux
        git fetch --no-tags linux-review oushixiong/drm-ast-radeon-amdgpu-for-ast-add-prime/20220811-115710
        git checkout 1b9b79a00132f2917ca66bea714a6f21fc939b0f
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=i386 SHELL=/bin/bash drivers/gpu/drm/ast/

If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>

sparse warnings: (new ones prefixed by >>)
   drivers/gpu/drm/ast/ast_drv.c:43:5: sparse: sparse: symbol 'ast_modeset' was not declared. Should it be static?
>> drivers/gpu/drm/ast/ast_drv.c:54:23: sparse: sparse: symbol 'ast_gem_prime_import_sg_table' was not declared. Should it be static?
--
   drivers/gpu/drm/ast/ast_mode.c:681:19: sparse: sparse: cast removes address space '__iomem' of expression
   drivers/gpu/drm/ast/ast_mode.c:681:16: sparse: sparse: incorrect type in assignment (different address spaces) @@     expected unsigned char [noderef] [usertype] __iomem *dstxor @@     got unsigned char [usertype] * @@
   drivers/gpu/drm/ast/ast_mode.c:681:16: sparse:     expected unsigned char [noderef] [usertype] __iomem *dstxor
   drivers/gpu/drm/ast/ast_mode.c:681:16: sparse:     got unsigned char [usertype] *
>> drivers/gpu/drm/ast/ast_mode.c:1759:33: sparse: sparse: incorrect type in argument 1 (different address spaces) @@     expected void volatile [noderef] __iomem * @@     got void * @@
   drivers/gpu/drm/ast/ast_mode.c:1759:33: sparse:     expected void volatile [noderef] __iomem *
   drivers/gpu/drm/ast/ast_mode.c:1759:33: sparse:     got void *
>> drivers/gpu/drm/ast/ast_mode.c:1713:5: sparse: sparse: symbol 'ast_handle_damage' was not declared. Should it be static?
>> drivers/gpu/drm/ast/ast_mode.c:1814:24: sparse: sparse: symbol 'ast_gem_fb_create_with_dirty' was not declared. Should it be static?

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp

  parent reply	other threads:[~2022-08-11 19:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-09 11:44 [PATCH] drm/ast: radeon amdgpu for ast add prime oushixiong
2022-08-09 11:44 ` oushixiong
2022-08-11 17:26 ` kernel test robot
2022-08-11 17:26   ` kernel test robot
2022-08-11 19:39 ` kernel test robot [this message]
2022-08-11 19:39   ` kernel test robot
  -- strict thread matches above, loose matches on Subject: below --
2022-08-09 11:52 oushixiong
2022-08-09 11:52 ` oushixiong
2022-08-10  1:02 oushixiong
2022-08-10  1:02 ` oushixiong
2022-08-10 14:53 ` kernel test robot
2022-08-10 14:53   ` 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=202208120345.REoTpw1K-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=airlied@linux.ie \
    --cc=airlied@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oushixiong@kylinos.cn \
    --cc=tzimmermann@suse.de \
    /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.