public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Imre Deak <imre.deak@intel.com>, intel-gfx@lists.freedesktop.org
Cc: kbuild-all@lists.01.org
Subject: Re: [Intel-gfx] [PATCH 2/5] drm/i915/adlp: Require always a power-of-two sized CCS surface stride
Date: Mon, 30 Aug 2021 10:29:51 +0800	[thread overview]
Message-ID: <202108301027.3XEM3foY-lkp@intel.com> (raw)
In-Reply-To: <20210827150955.3343520-3-imre.deak@intel.com>

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

Hi Imre,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on drm-tip/drm-tip]
[cannot apply to drm-intel/for-linux-next v5.14 next-20210827]
[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/Imre-Deak/drm-i915-adlp-Add-support-for-remapping-CCS-FBs/20210827-231214
base:   git://anongit.freedesktop.org/drm/drm-tip drm-tip
config: x86_64-rhel-8.3-kselftests (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.3-348-gf0e6938b-dirty
        # https://github.com/0day-ci/linux/commit/ebed87d6cd7dc951ce86f16fa1a438382d14d443
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Imre-Deak/drm-i915-adlp-Add-support-for-remapping-CCS-FBs/20210827-231214
        git checkout ebed87d6cd7dc951ce86f16fa1a438382d14d443
        # save the attached .config to linux build tree
        make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=x86_64 SHELL=/bin/bash

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


sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/i915/display/intel_fb.c:78:14: sparse: sparse: symbol 'gen12_ccs_aux_stride' was not declared. Should it be static?

Please review and possibly fold the followup patch.

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

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 42190 bytes --]

  parent reply	other threads:[~2021-08-30  2:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-27 15:09 [Intel-gfx] [PATCH 0/5] drm/i915/adlp: Add support for remapping CCS FBs Imre Deak
2021-08-27 15:09 ` [Intel-gfx] [PATCH 1/5] drm/i915: Use tile block based dimensions for CCS origin x, y check Imre Deak
2021-08-27 15:09 ` [Intel-gfx] [PATCH 2/5] drm/i915/adlp: Require always a power-of-two sized CCS surface stride Imre Deak
2021-08-27 22:31   ` kernel test robot
2021-08-28  0:50   ` kernel test robot
2021-08-30  2:29   ` kernel test robot [this message]
2021-08-30  2:29   ` [Intel-gfx] [RFC PATCH] drm/i915/adlp: gen12_ccs_aux_stride() can be static kernel test robot
2021-08-27 15:09 ` [Intel-gfx] [PATCH 3/5] drm/i915/adlp: Assert that VMAs in DPT start at 0 Imre Deak
2021-08-27 15:09 ` [Intel-gfx] [PATCH 4/5] drm/i915: Follow a new->old platform check order in intel_fb_stride_alignment Imre Deak
2021-08-27 15:09 ` [Intel-gfx] [PATCH 5/5] drm/i915/adlp: Add support for remapping CCS FBs Imre Deak
2021-09-04 11:54   ` Juha-Pekka Heikkila
2021-09-05 10:55     ` Imre Deak
2021-08-27 16:08 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2021-08-27 16:10 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-08-27 16:53 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2021-08-27 17:45   ` Imre Deak
2021-08-27 23:41     ` Vudum, Lakshminarayana
2021-08-27 23:38 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-08-28  1:05 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=202108301027.3XEM3foY-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=imre.deak@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=kbuild-all@lists.01.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