From: Julia Lawall <julia.lawall@lip6.fr>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org,
Daniel Vetter <daniel.vetter@ffwll.ch>,
stable@vger.kernel.org, kbuild-all@01.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Disable stolen on 865G (fwd)
Date: Thu, 4 Aug 2016 13:38:51 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.10.1608041337460.7967@hadrien> (raw)
[-- Attachment #1: Type: TEXT/PLAIN, Size: 2754 bytes --]
An extra tab would help avoid misunderstandings.
julia
---------- Forwarded message ----------
Date: Thu, 4 Aug 2016 19:33:05 +0800
From: kbuild test robot <fengguang.wu@intel.com>
To: kbuild@01.org
Cc: Julia Lawall <julia.lawall@lip6.fr>
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Disable stolen on 865G
CC: kbuild-all@01.org
In-Reply-To: <1470304564-9842-1-git-send-email-chris@chris-wilson.co.uk>
TO: Chris Wilson <chris@chris-wilson.co.uk>
CC: intel-gfx@lists.freedesktop.org, Daniel Vetter <daniel.vetter@ffwll.ch>, stable@vger.kernel.org
CC: Daniel Vetter <daniel.vetter@ffwll.ch>, stable@vger.kernel.org
Hi Chris,
[auto build test WARNING on drm-intel/for-linux-next]
[also build test WARNING on v4.7 next-20160804]
[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/Chris-Wilson/drm-i915-Disable-stolen-on-865G/20160804-175832
base: git://anongit.freedesktop.org/drm-intel for-linux-next
:::::: branch date: 2 hours ago
:::::: commit date: 2 hours ago
>> drivers/gpu/drm/i915/i915_gem_stolen.c:126:2-24: code aligned with following code on line 129
git remote add linux-review https://github.com/0day-ci/linux
git remote update linux-review
git checkout d0f0edcafdb2b2e5ab8699658c6eb4de98c2cda3
vim +126 drivers/gpu/drm/i915/i915_gem_stolen.c
0ad98c74e Ville Syrj�l� 2015-10-08 120 /*
0ad98c74e Ville Syrj�l� 2015-10-08 121 * FIXME is the graphics stolen memory region
0ad98c74e Ville Syrj�l� 2015-10-08 122 * always at TOUD? Ie. is it always the last
0ad98c74e Ville Syrj�l� 2015-10-08 123 * one to be allocated by the BIOS?
0ad98c74e Ville Syrj�l� 2015-10-08 124 */
d0f0edcaf Chris Wilson 2016-08-04 125 if (0) /* https://bugs.freedesktop.org/show_bug.cgi?id=96473 */
0ad98c74e Ville Syrj�l� 2015-10-08 @126 pci_bus_read_config_word(dev->pdev->bus, PCI_DEVFN(0, 0),
0ad98c74e Ville Syrj�l� 2015-10-08 127 I865_TOUD, &toud);
0ad98c74e Ville Syrj�l� 2015-10-08 128
0ad98c74e Ville Syrj�l� 2015-10-08 @129 base = toud << 16;
0ad98c74e Ville Syrj�l� 2015-10-08 130 } else if (IS_I85X(dev)) {
0ad98c74e Ville Syrj�l� 2015-10-08 131 u32 tseg_size = 0;
0ad98c74e Ville Syrj�l� 2015-10-08 132 u32 tom;
:::::: The code at line 126 was first introduced by commit
:::::: 0ad98c74e093041eb163b01013eb46989f2124aa drm/i915: Determine the stolen memory base address on gen2
:::::: TO: Ville Syrj�l� <ville.syrjala@linux.intel.com>
:::::: CC: Daniel Vetter <daniel.vetter@ffwll.ch>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
reply other threads:[~2016-08-04 11:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=alpine.DEB.2.10.1608041337460.7967@hadrien \
--to=julia.lawall@lip6.fr \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kbuild-all@01.org \
--cc=stable@vger.kernel.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