All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Repentin <nicolas@shivaserv.fr>
To: Jani Nikula <jani.nikula@linux.intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: Fixing i915/opregion issues with firmware which lists more then 8 output devices
Date: Wed, 23 Mar 2016 18:04:32 +0100	[thread overview]
Message-ID: <56F2CCA0.40100@shivaserv.fr> (raw)
In-Reply-To: <87y499pgrp.fsf@intel.com>


[-- Attachment #1.1: Type: text/plain, Size: 608 bytes --]

Thanks ;)

I'm sorry, but do you have a "howto" for doing this?

Not very familiar with patching things.

Nicolas

Le 23/03/2016 12:36, Jani Nikula a écrit :
> On Tue, 22 Mar 2016, Nicolas Repentin <nicolas@shivaserv.fr> wrote:
>> I'm searching for a fix for thread
>> http://www.spinics.net/lists/intel-gfx/msg79628.html
>>
>> Does someone know how to ask the intel drm team to fix this issue?
> You just have. ;)
>
> Please try this patch series [1]. It's untested, but might
> help. Feedback appreciated.
>
> BR,
> Jani.
>
>
> [1] https://patchwork.freedesktop.org/series/4783/
>

[-- Attachment #1.2: Type: text/html, Size: 1412 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

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

  reply	other threads:[~2016-03-23 17:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-22 16:24 Fixing i915/opregion issues with firmware which lists more then 8 output devices Nicolas Repentin
2016-03-23 11:36 ` Jani Nikula
2016-03-23 17:04   ` Nicolas Repentin [this message]
2016-03-24  8:36     ` Jani Nikula
2016-04-15 17:35   ` Nicolas Repentin
2016-04-18  7:44     ` Jani Nikula
  -- strict thread matches above, loose matches on Subject: below --
2016-08-30 12:55 tasev.stefanoska
2016-04-26 11:28 thermatk(EZN)
2016-04-25 18:19 Ruslan Boitsov
2015-11-05 16:05 Hans de Goede
2015-11-06 10:19 ` Jani Nikula
2015-11-06 10:20   ` Hans de Goede
2015-11-13 18:41     ` Jani Nikula
2016-03-23 11:48     ` Jani Nikula
2016-03-23 12:57       ` Hans de Goede

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=56F2CCA0.40100@shivaserv.fr \
    --to=nicolas@shivaserv.fr \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@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 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.