All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
Cc: intel-gfx@lists.freedesktop.org, kbuild-all@01.org
Subject: Re: [PATCH 1/6] drm/i915/uc: move uC WOPCM setup in uc_init_hw
Date: Wed, 31 Jul 2019 04:24:02 +0800	[thread overview]
Message-ID: <201907310348.jzOxWgAi%lkp@intel.com> (raw)
In-Reply-To: <20190729234727.28286-2-daniele.ceraolospurio@intel.com>

Hi Daniele,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on drm-intel/for-linux-next]
[cannot apply to v5.3-rc2 next-20190730]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Daniele-Ceraolo-Spurio/Call-uC-functions-from-GT-ones/20190730-131043
base:   git://anongit.freedesktop.org/drm-intel for-linux-next
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.1-rc1-7-g2b96cd8-dirty
        make ARCH=x86_64 allmodconfig
        make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'

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


sparse warnings: (new ones prefixed by >>)

>> drivers/gpu/drm/i915/gt/uc/intel_uc.c:410:5: sparse: sparse: symbol 'uc_wopcm_init_hw' was not declared. Should it be static?

Please review and possibly fold the followup patch.

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2019-07-30 20:24 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-29 23:47 [PATCH 0/6] Call uC functions from GT ones Daniele Ceraolo Spurio
2019-07-29 23:47 ` [PATCH 1/6] drm/i915/uc: move uC WOPCM setup in uc_init_hw Daniele Ceraolo Spurio
2019-07-30 14:39   ` Michal Wajdeczko
2019-07-30 21:04     ` Daniele Ceraolo Spurio
2019-07-30 20:24   ` kbuild test robot [this message]
2019-07-30 20:24   ` [RFC PATCH] drm/i915/uc: uc_wopcm_init_hw() can be static kbuild test robot
2019-07-29 23:47 ` [PATCH 2/6] drm/i915: move gt_cleanup_early out of gem_cleanup_early Daniele Ceraolo Spurio
2019-07-30  7:19   ` Tvrtko Ursulin
2019-07-30  8:01     ` Chris Wilson
2019-07-30 14:56       ` Daniele Ceraolo Spurio
2019-07-30 15:12         ` Chris Wilson
2019-07-29 23:47 ` [PATCH 3/6] drm/i915/uc: move uc early functions inside the gt ones Daniele Ceraolo Spurio
2019-07-30 14:53   ` Michal Wajdeczko
2019-07-29 23:47 ` [PATCH 4/6] drm/i915/gt: introduce intel_gt_runtime_suspend/resume Daniele Ceraolo Spurio
2019-07-30  7:35   ` Tvrtko Ursulin
2019-07-29 23:47 ` [PATCH 5/6] drm/i915/uc: move uc_resume under gt_resume Daniele Ceraolo Spurio
2019-07-30  8:09   ` Chris Wilson
2019-07-29 23:47 ` [PATCH 6/6] drm/i915/gt: introduce intel_gt_suspend Daniele Ceraolo Spurio
2019-07-30  7:33   ` Tvrtko Ursulin
2019-07-30  8:12     ` Chris Wilson
2019-07-30 14:58       ` Daniele Ceraolo Spurio
2019-07-30  0:44 ` ✗ Fi.CI.SPARSE: warning for Call uC functions from GT ones Patchwork
2019-07-30  1:03 ` ✓ Fi.CI.BAT: success " Patchwork
2019-07-30 12:20 ` ✓ 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=201907310348.jzOxWgAi%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=daniele.ceraolospurio@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=kbuild-all@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 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.