From: Jani Nikula <jani.nikula@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Always load guc by default.
Date: Thu, 24 Nov 2016 10:31:50 +0200 [thread overview]
Message-ID: <8760ndz3bd.fsf@intel.com> (raw)
In-Reply-To: <20161124082123.GD6546@nuc-i3427.alporthouse.com>
On Thu, 24 Nov 2016, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> History says we will regret enabling a new piece of hw/fw without a
> feature option.
And history says we'll regret adding new module parameters for
everything. Lose-lose. :(
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2016-11-24 8:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-24 0:52 [PATCH] drm/i915: Always load guc by default Anusha Srivatsa
2016-11-24 7:13 ` Chris Wilson
2016-11-24 8:15 ` Tvrtko Ursulin
2016-11-24 8:21 ` Chris Wilson
2016-11-24 8:31 ` Tvrtko Ursulin
2016-11-24 8:41 ` Chris Wilson
2016-12-02 18:11 ` Srivatsa, Anusha
2016-12-03 16:39 ` Chris Wilson
2016-11-24 8:31 ` Jani Nikula [this message]
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=8760ndz3bd.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tvrtko.ursulin@linux.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