From: Jani Nikula <jani.nikula@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org, shuang.he@linux.intel.com
Subject: Re: [PATCH 1/2] drm/i915: allow dev_priv for HAS_PCH_* macros too
Date: Fri, 10 Oct 2014 18:10:41 +0300 [thread overview]
Message-ID: <877g08rmdq.fsf@intel.com> (raw)
In-Reply-To: <20141010145849.GT12897@nuc-i3427.alporthouse.com>
On Fri, 10 Oct 2014, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> On Fri, Oct 10, 2014 at 05:53:32PM +0300, Jani Nikula wrote:
>> Follow-up to
>> commit dbbe91279511d6a18a521b953a3c139e4787e660
>> Author: Chris Wilson <chris@chris-wilson.co.uk>
>> Date: Sat Aug 9 19:18:43 2014 +0100
>>
>> drm/i915: Agnostic INTEL_INFO
>>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>
> If you look at
>
> 1408905331-22455-1-git-send-email-chris@chris-wilson.co.uk
>
> you will find another one suitable for conversion as well
Thanks, I missed that. I just added my r-b.
Daniel, please pick that one up instead of 1/2 as a prerequisite for
2/2.
BR,
Jani.
> -Chris
>
> --
> Chris Wilson, Intel Open Source Technology Centre
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2014-10-10 15:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 14:53 [PATCH 1/2] drm/i915: allow dev_priv for HAS_PCH_* macros too Jani Nikula
2014-10-10 14:53 ` [PATCH 2/2] drm/i915: spt does not have pch backlight override bit Jani Nikula
2014-10-11 8:28 ` [PATCH 2/2] drm/i915: spt does not have pch backlight shuang.he
2014-10-20 11:28 ` [PATCH 2/2] drm/i915: spt does not have pch backlight override bit Ville Syrjälä
2014-10-10 14:58 ` [PATCH 1/2] drm/i915: allow dev_priv for HAS_PCH_* macros too Chris Wilson
2014-10-10 15:10 ` Jani Nikula [this message]
2014-10-21 14:57 ` 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=877g08rmdq.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=shuang.he@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