public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Michael Cheng <michael.cheng@intel.com>, intel-gfx@lists.freedesktop.org
Cc: kbuild-all@lists.01.org, lucas.demarchi@intel.com,
	dri-devel@lists.freedesktop.org, michael.cheng@intel.com
Subject: Re: [Intel-gfx] [PATCH v11 1/6] drm: Add arch arm64 for drm_clflush_virt_range
Date: Wed, 23 Feb 2022 17:56:50 +0800	[thread overview]
Message-ID: <202202231707.Syvm9oFu-lkp@intel.com> (raw)
In-Reply-To: <20220223055900.415627-2-michael.cheng@intel.com>

Hi Michael,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on drm-tip/drm-tip]
[also build test WARNING on drm/drm-next]
[cannot apply to drm-intel/for-linux-next v5.17-rc5 next-20220222]
[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]

url:    https://github.com/0day-ci/linux/commits/Michael-Cheng/Use-drm_clflush-instead-of-clflush/20220223-140110
base:   git://anongit.freedesktop.org/drm/drm-tip drm-tip
config: h8300-randconfig-r014-20220221 (https://download.01.org/0day-ci/archive/20220223/202202231707.Syvm9oFu-lkp@intel.com/config)
compiler: h8300-linux-gcc (GCC) 11.2.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/0day-ci/linux/commit/f4c92ba1f52db578a26ac9944e2cbe52c548e8e9
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Michael-Cheng/Use-drm_clflush-instead-of-clflush/20220223-140110
        git checkout f4c92ba1f52db578a26ac9944e2cbe52c548e8e9
        # save the config file to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=h8300 SHELL=/bin/bash drivers/gpu/drm/

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/gpu/drm/drm_cache.c:31:
>> include/linux/cacheflush.h:12:46: warning: 'struct folio' declared inside parameter list will not be visible outside of this definition or declaration
      12 | static inline void flush_dcache_folio(struct folio *folio)
         |                                              ^~~~~


vim +12 include/linux/cacheflush.h

522a0032af00550 Matthew Wilcox (Oracle  2021-11-06   6) 
522a0032af00550 Matthew Wilcox (Oracle  2021-11-06   7) #if ARCH_IMPLEMENTS_FLUSH_DCACHE_PAGE
522a0032af00550 Matthew Wilcox (Oracle  2021-11-06   8) #ifndef ARCH_IMPLEMENTS_FLUSH_DCACHE_FOLIO
522a0032af00550 Matthew Wilcox (Oracle  2021-11-06   9) void flush_dcache_folio(struct folio *folio);
522a0032af00550 Matthew Wilcox (Oracle  2021-11-06  10) #endif
522a0032af00550 Matthew Wilcox (Oracle  2021-11-06  11) #else
522a0032af00550 Matthew Wilcox (Oracle  2021-11-06 @12) static inline void flush_dcache_folio(struct folio *folio)
522a0032af00550 Matthew Wilcox (Oracle  2021-11-06  13) {
522a0032af00550 Matthew Wilcox (Oracle  2021-11-06  14) }
522a0032af00550 Matthew Wilcox (Oracle  2021-11-06  15) #define ARCH_IMPLEMENTS_FLUSH_DCACHE_FOLIO 0
522a0032af00550 Matthew Wilcox (Oracle  2021-11-06  16) #endif /* ARCH_IMPLEMENTS_FLUSH_DCACHE_PAGE */
522a0032af00550 Matthew Wilcox (Oracle  2021-11-06  17) 

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

  reply	other threads:[~2022-02-23  9:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-23  5:58 [Intel-gfx] [PATCH v11 0/6] Use drm_clflush* instead of clflush Michael Cheng
2022-02-23  5:58 ` [Intel-gfx] [PATCH v11 1/6] drm: Add arch arm64 for drm_clflush_virt_range Michael Cheng
2022-02-23  9:56   ` kernel test robot [this message]
2022-02-23 12:46   ` kernel test robot
2022-02-23 17:43   ` kernel test robot
2022-02-23  5:58 ` [Intel-gfx] [PATCH v11 2/6] drm/i915/gt: Re-work intel_write_status_page Michael Cheng
2022-02-23  5:58 ` [Intel-gfx] [PATCH v11 3/6] drm/i915/gt: Drop invalidate_csb_entries Michael Cheng
2022-02-23  5:58 ` [Intel-gfx] [PATCH v11 4/6] drm/i915/gt: Re-work reset_csb Michael Cheng
2022-02-23  5:58 ` [Intel-gfx] [PATCH v11 5/6] drm/i915/: Re-work clflush_write32 Michael Cheng
2022-02-23  5:59 ` [Intel-gfx] [PATCH v11 6/6] drm/i915/gt: replace cache_clflush_range Michael Cheng
2022-02-23  8:09 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Use drm_clflush* instead of clflush (rev10) Patchwork
2022-02-23  8:10 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-02-23  8:38 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-02-24  4:03 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Use drm_clflush* instead of clflush (rev11) Patchwork
2022-02-24  4:05 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-02-24  4:35 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-02-24 16:40 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork

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=202202231707.Syvm9oFu-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=kbuild-all@lists.01.org \
    --cc=lucas.demarchi@intel.com \
    --cc=michael.cheng@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