intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	Mika Kahola <mika.kahola@intel.com>,
	intel-gfx@lists.freedesktop.org,
	Rodrigo Vivi <rodrigo.vivi@gmail.com>
Cc: jaswinder@perfectintelligent.com, fritsch@xbmc.org
Subject: Re: [PATCH v2] drm/i915: Check for fused or unused pipes
Date: Tue, 30 Jan 2018 09:36:06 +0200	[thread overview]
Message-ID: <87d11rajdl.fsf@intel.com> (raw)
In-Reply-To: <151725840073.10214.9007892616809331533@mail.alporthouse.com>

On Mon, 29 Jan 2018, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> Quoting Jani Nikula (2018-01-19 14:22:49)
>> On Mon, 18 Dec 2017, Mika Kahola <mika.kahola@intel.com> wrote:
>> > We may have fused or unused pipes in our system. Let's check that the pipe
>> > in question is within limits of accessible pipes. In case, that we are not
>> > able to access the pipe, we return early with a warning.
>> >
>> > v2: Rephrasing of the commit message (Jani)
>> >
>> > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=103206
>> > Reported-by: Thomas Gleixner <tglx@linutronix.de>
>> > Tested-by: Jaswinder Singh Rajput <jaswinder@perfectintelligent.com>
>> > Suggested-by: Jani Nikula <jani.nikula@intel.com>
>> > Reviewed-by: Jani Nikula <jani.nikula@intel.com>
>> > Signed-off-by: Mika Kahola <mika.kahola@intel.com>
>> 
>> Pushed, thanks for the patch, sorry for the delay.
>
> This WARN is in the wild, should we queue this for drm-intel-fixes.
>
> Reported-by: fritsch@xbmc.org

Rodrigo, please cherry-pick this to drm-intel-next-fixes, with Cc:
stable, with any other cherry-picks you might have, and send a pull
request to Dave to merge either during the merge window or at -rc1.

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

  reply	other threads:[~2018-01-30  7:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-18  8:04 [PATCH v2] drm/i915: Check for fused or unused pipes Mika Kahola
2017-12-18  8:30 ` ✓ Fi.CI.BAT: success for drm/i915: Check for fused or unused pipes (rev3) Patchwork
2017-12-18  9:40 ` ✗ Fi.CI.IGT: failure " Patchwork
2018-01-19 14:22 ` [PATCH v2] drm/i915: Check for fused or unused pipes Jani Nikula
2018-01-29 20:40   ` Chris Wilson
2018-01-30  7:36     ` Jani Nikula [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-12-15 13:56 Mika Kahola
2017-12-15 15:32 ` Jani Nikula

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=87d11rajdl.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=fritsch@xbmc.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jaswinder@perfectintelligent.com \
    --cc=mika.kahola@intel.com \
    --cc=rodrigo.vivi@gmail.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;
as well as URLs for NNTP newsgroup(s).