From: Jani Nikula <jani.nikula@linux.intel.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Damien Lespiau <damien.lespiau@intel.com>
Cc: Daniel Vetter <daniel.vetter@intel.com>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] drivers/gpu/drm/i915/i915_gem_gtt.c
Date: Mon, 25 May 2015 08:32:07 +0300 [thread overview]
Message-ID: <87mw0ti5ns.fsf@intel.com> (raw)
In-Reply-To: <20150523100345.9abce839.akpm@linux-foundation.org>
On Sat, 23 May 2015, Andrew Morton <akpm@linux-foundation.org> wrote:
> On Sat, 23 May 2015 14:30:09 +0100 Damien Lespiau <damien.lespiau@intel.com> wrote:
>
>> On Fri, May 22, 2015 at 02:17:32PM -0700, Andrew Morton wrote:
>> > I'm not sure what's happened to the drm code in linux-next - it's
>> > exploding all over the place. Did someone turn on -Werror without
>> > doing anywhere near enough testing?
>> >
>> > Anyway, I don't know how to fix this i386 build error:
>>
>> Seems like you have CONFIG_DRM_I915_WERROR set?
>
> Yes.
>
>> We explicitely made sure to not enable -Werror by default,
>
> `make allmodconfig' enables CONFIG_DRM_I915_WERROR.
Right.
> I'm not sure what is the approved way of fixing this. Perhaps
> disabling CONFIG_DRM_I915_WERROR when CONFIG_COMPILE_TEST=y.
Maybe the answer right now is to just drop that config. Daniel?
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-05-25 5:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 21:17 drivers/gpu/drm/i915/i915_gem_gtt.c Andrew Morton
2015-05-23 13:30 ` drivers/gpu/drm/i915/i915_gem_gtt.c Damien Lespiau
2015-05-23 17:03 ` drivers/gpu/drm/i915/i915_gem_gtt.c Andrew Morton
2015-05-25 5:32 ` Jani Nikula [this message]
2015-05-26 5:45 ` drivers/gpu/drm/i915/i915_gem_gtt.c Daniel Vetter
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=87mw0ti5ns.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=damien.lespiau@intel.com \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.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