public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Nick Hoath <nicholas.hoath@intel.com>
Cc: intel-gfx@lists.freedesktop.org, kbuild-all@01.org
Subject: Re: [PATCH 4/6] drm/i915: Improve dynamic management/eviction of lrc backing objects
Date: Tue, 20 Oct 2015 18:14:04 +0800	[thread overview]
Message-ID: <201510201848.ovU2CnIW%fengguang.wu@intel.com> (raw)
In-Reply-To: <1445333036-22164-5-git-send-email-nicholas.hoath@intel.com>

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

Hi Nick,

[auto build test WARNING on next-20151020 -- if it's inappropriate base, please suggest rules for selecting the more suitable base]

url:    https://github.com/0day-ci/linux/commits/Nick-Hoath/lrc-lifecycle-cleanups/20151020-173347
config: i386-randconfig-x009-10191220 (attached as .config)
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

All warnings (new ones prefixed by >>):

   drivers/gpu/drm/i915/i915_gem_gtt.c: In function 'i915_vma_bind':
>> drivers/gpu/drm/i915/i915_gem_gtt.c:3523:4: warning: ignoring return value of 'i915_vma_unbind', declared with attribute warn_unused_result [-Wunused-result]
       i915_vma_unbind(vma);
       ^

vim +/i915_vma_unbind +3523 drivers/gpu/drm/i915/i915_gem_gtt.c

  3507							 vma->node.start,
  3508							 vma->node.size);
  3509			vma->pin_count--;
  3510			if (ret)
  3511				return ret;
  3512		}
  3513	
  3514		ret = vma->vm->bind_vma(vma, cache_level, bind_flags);
  3515		if (ret)
  3516			return ret;
  3517	
  3518		vma->bound |= bind_flags;
  3519	
  3520		if (vma->obj->mmap) {
  3521			ret = vma->obj->mmap(vma->obj, false);
  3522			if (ret) {
> 3523				i915_vma_unbind(vma);
  3524				return ret;
  3525			}
  3526		}
  3527	
  3528		return 0;
  3529	}
  3530	
  3531	/**

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 26282 bytes --]

[-- Attachment #3: Type: text/plain, Size: 159 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2015-10-20 10:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-20  9:23 [PATCH 0/6] lrc lifecycle cleanups Nick Hoath
2015-10-20  9:23 ` [PATCH 1/6] drm/i195: Rename gt_irq_handler variable Nick Hoath
2015-10-20  9:23 ` [PATCH 2/6] drm/i915: Break out common code from gen8_gt_irq_handler Nick Hoath
2015-10-20 12:12   ` Daniel Vetter
2015-10-20 12:40     ` Chris Wilson
2015-10-20  9:23 ` [PATCH 3/6] drm/i915: Unify execlist and legacy request life-cycles Nick Hoath
2015-10-20  9:53   ` Chris Wilson
2015-10-20  9:23 ` [PATCH 4/6] drm/i915: Improve dynamic management/eviction of lrc backing objects Nick Hoath
2015-10-20  9:54   ` Chris Wilson
2015-10-20 10:14   ` kbuild test robot [this message]
2015-10-20  9:23 ` [PATCH 5/6] drm/i915: Add the CPU mapping of the hw context to the pinned items Nick Hoath
2015-10-20  9:56   ` Chris Wilson
2015-10-20  9:23 ` [PATCH 6/6] drm/i915: Only update ringbuf address when necessary Nick Hoath

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=201510201848.ovU2CnIW%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=kbuild-all@01.org \
    --cc=nicholas.hoath@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